distill-pr-intent

Name: distill-pr-intent
Author: openclaw

将单个 OpenClaw PR 无副作用提炼为简短意图备忘录，便于快速理解变更目的。

星标

★ 158

来源

GitHub

更新于

2026-10-20

// 安全评估低风险

仅提示词，不执行代码
开源可审计
社区验证· 158

正在进行安全审计…

凭证密钥
网络外发
代码执行
数据访问
来源供应链

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "distill-pr-intent" 技能：
1. 下载 https://raw.githubusercontent.com/openclaw/clawdinators/main/clawdinator/workspace/skills/distill-pr-intent/SKILL.md
2. 保存为 ~/.claude/skills/distill-pr-intent/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 用法示例

快速理解 PR 目的

输入

请将这个 OpenClaw PR 提炼成一份简短意图备忘录，说明它解决的问题、核心改动方向、预期影响，以及任何明显的风险或待确认点。只输出精炼结论，不要执行任何修改操作。

预期产出

一份简洁备忘录，概括该 PR 的目标、改动意图、影响范围与潜在风险。

为评审前做摘要

输入

阅读这个单独 PR 的内容，生成一段适合代码评审前阅读的意图摘要，重点写明为什么要改、改了哪一类内容、哪些模块可能受到影响。请保持客观简短。

预期产出

适合评审者快速浏览的 PR 意图摘要，帮助提前建立上下文。

整理变更沟通说明

输入

基于这个 OpenClaw PR，输出一份面向产品和开发沟通的意图说明，分别用一句话总结业务目的和技术目的，并补充可能需要关注的后续事项。

预期产出

一份便于跨角色沟通的简短说明，包含业务意图、技术意图和后续关注点。

// 文档

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: ....