distill-pr-intent

Name: distill-pr-intent
Author: openclaw

Distill a single OpenClaw PR into a short intent memo safely.

Stars

★ 157

Source

GitHub

Updated

2026-06-27

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 157

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "distill-pr-intent" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/clawdinators/main/clawdinator/workspace/skills/distill-pr-intent/SKILL.md
2. Save it as ~/.claude/skills/distill-pr-intent/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Quickly understand a PR's purpose

Prompt

Please distill this OpenClaw PR into a short intent memo describing the problem it solves, the main change direction, expected impact, and any obvious risks or open questions. Output concise conclusions only and do not perform any modifications.

Expected

A concise memo summarizing the PR's goal, intent, scope of impact, and potential risks.

Create a pre-review summary

Prompt

Read this single PR and generate an intent summary suitable for pre-review reading. Focus on why the change is needed, what kind of changes were made, and which modules may be affected. Keep it objective and brief.

Expected

A reviewer-friendly PR intent summary that helps establish context quickly.

Prepare change communication notes

Prompt

Based on this OpenClaw PR, produce an intent note for product and engineering communication. Summarize the business purpose and technical purpose in one sentence each, and add any follow-up items that may need attention.

Expected

A short cross-functional note covering business intent, technical intent, and follow-up considerations.

// docs

Distill PR Intent (single PR, stdout-only)

Goal

Given one PR number in openclaw/openclaw, output a short memo answering:

What was the author trying to accomplish (motivation / problem framing / bet), as evidenced by the code change?

Inputs

Required: PR number (assume repo openclaw/openclaw).

Rules

No external side effects: no comments, labels, merges, pushes.
Prefer code-derived intent. PR title/body are secondary.
Do not guess. If intent is unclear from artifacts, say so.
Keep output short + stable. No telemetry/timing in the memo.

Output format (stdout)

PR INTENT (openclaw#<PR>)

<free prose, up to ~5 sentences; keep under ~10 lines>

Mechanical steps (deterministic)

Work in the OpenClaw repo worktree tooling:

cd /var/lib/clawd/repos/openclaw
scripts/pr review-init <PR>
scripts/pr review-checkout-pr <PR>

source .local/review-context.env

Gather diff artifacts:

git diff --name-status "$MERGE_BASE"..HEAD > .local/intent.name-status.txt
git diff --stat "$MERGE_BASE"..HEAD > .local/intent.stat.txt

# Patch budget: 200KB
patch_bytes=$(git diff "$MERGE_BASE"..HEAD | wc -c | tr -d ' ')
if [ "$patch_bytes" -le 200000 ]; then
  git diff "$MERGE_BASE"..HEAD > .local/intent.patch.txt
  echo PATCH_OK > .local/intent.patch-mode.txt
else
  : > .local/intent.patch.txt
  echo TOO_LONG > .local/intent.patch-mode.txt
fi

Distill intent:

If PATCH_OK: infer intent from .local/intent.patch.txt.
If TOO_LONG: infer intent from .local/intent.name-status.txt + .local/intent.stat.txt.

If multiple intents exist, mention 2–3 briefly.

If nothing coherent: say Intent unclear: ....