ai-diff-reviewer-apply-review
Read the most recent AI Diff Reviewer review from the current branch's open PR, present the findings in the same format as the parent skill's local review flow (verdict → findings table → per-finding body → recommendation), and — with explicit consent — walk the developer through each finding to apply, defer, or skip. Multi-provider aware — when the repo runs a matrix of legs (anthropic, cursor, codex, claude-code), attributes each finding to its self-reviewed provider label and surfaces cross-leg consensus. Anchors on the latest ai-pr-reviewer-marker tracking comment and filters minimized (collapsed / outdated) comments per the repo's documented PR-review workflow. Read-only by default; edits to source files require an explicit yes per finding, never commits, never pushes. Use when the developer says "what did the CI review say?", "read the review on this PR", "apply the AI review's fixes", "walk me through the findings", "which findings blocked the merge?", "show me only the critical
DailybotHQ · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add DailybotHQ/deepworkplan-skill --skill ai-diff-reviewer-apply-review技能说明
name: ai-diff-reviewer-apply-review description: Read the most recent AI Diff Reviewer review from the current branch's open PR, present the findings in the same format as the parent skill's local review flow (verdict → findings table → per-finding body → recommendation), and — with explicit consent — walk the developer through each finding to apply, defer, or skip. Multi-provider aware — when the repo runs a matrix of legs (anthropic, cursor, codex, claude-code), attributes each finding to its self-reviewed provider label and surfaces cross-leg consensus. Anchors on the latest ai-pr-reviewer-marker tracking comment and filters minimized (collapsed / outdated) comments per the repo's documented PR-review workflow. Read-only by default; edits to source files require an explicit yes per finding, never commits, never pushes. Use when the developer says "what did the CI review say?", "read the review on this PR", "apply the AI review's fixes", "walk me through the findings", "which findings blocked the merge?", "show me only the critical findings", or "the bot posted a review — help me address it". version: "2.0.1" documentation_url: https://github.com/DailybotHQ/ai-diff-reviewer/blob/main/skills/ai-diff-reviewer/apply-review/SKILL.md user-invocable: true metadata: {"openclaw":{"emoji":"🔎","homepage":"https://github.com/DailybotHQ/ai-diff-reviewer","requires":{"anyBins":["git","gh"]}}} allowed-tools: Bash, Read, Grep, Glob, Edit
AI Diff Reviewer — Apply Review (sub-skill)
Companion to the ai-diff-reviewer skill. Where the
parent runs the review locally and open-pr
writes the pull request, this sub-skill closes the loop: it
reads the review the CI Action posted back on the PR, presents
the findings in the same format the local review uses, and — with
explicit consent — walks the developer through each finding to
apply, defer, or skip.
The design philosophy mirrors the family's:
- Parity of shape. The output uses the same
verdict → findings table → per-finding body → notes → recommendationstructure the parent skill emits. A developer who has seen one of the two knows how to read the other. When the CI leg found "SQL injection insrc/auth.ts:55", the summary looks identical whether it was your local agent or CI that surfaced it. - Read-only by default. Fetching + presenting the review never writes anything. Only when the developer explicitly asks to "walk through" or "apply the fixes" does the sub-skill open source files, and each individual apply still requires a yes.
- Multi-provider aware. This repo (and any consumer that opts
into the 4-leg matrix) posts up to four independent reviews per PR,
distinguished by
self-reviewed:<provider>labels. The sub-skill reads all live legs, attributes each finding to its leg, and surfaces cross-leg consensus ("agreed by 3/3 legs → strong signal; called by 1/3 → could be leg-specific"). - Never commits, never pushes. Applied fixes stay unstaged in the
working tree. Commit + push is the developer's judgment call,
matching
open-pr's trust boundary.
The single source of truth for the workflow this sub-skill implements
is docs/PR_REVIEW_WORKFLOW.md.
This sub-skill is that doc, executable.
When it fires
Read + present the review (default flow) — triggers:
- "What did the CI review say?"
- "Read the review on this PR"
- "Show me the review findings"
- "Did the bot approve or request changes?"
- "Which findings blocked the merge?"
- "The AI review just landed — summarize it"
Walkthrough mode (apply/defer/skip per finding) — triggers:
- "Apply the AI review's fixes"
- "Walk me through the findings"
- "Go through the review one finding at a time"
- "Help me address the critical findings"
- "Fix the review comments the bot left"
Scope filters — triggers:
- "Critical only" / "show me only the critical findings"
- "Warnings only" / "info-level only"
- "Just the ones from the
cursorleg" (multi-leg attribution) - "The findings we all three legs agreed on"
Fall through to a sibling skill when the developer:
- Wants a local review on uncommitted changes → parent
ai-diff-reviewerskill (default review flow). This sub-skill reads reviews that already exist on the PR; the parent produces a new one locally. - Wants to install the CI action →
setup. - Wants to customize the reviewer →
generate-extension. - Wants to author or refresh the PR body →
open-pr. - Wants to read human reviewer comments (not the bot's) → defer;
this skill filters to bot artefacts by design.
gh pr view --commentscovers human threads.
If the intent is ambiguous ("show me the review" on a repo where the Action posted 4 legs, or on a PR with both bot findings and human comments), ask ONE clarifying question before acting.
Step 0 — Trust boundary
This sub-skill's reads and writes are enumerated below. Nothing else happens.
Reads (always allowed, no consent needed):
git:git branch --show-current,git rev-parse HEAD,git status, andgit show <marker-sha>:<path>— the latter is Step 6b's primary pre-image source (used on everyapply, not just the empty-diffHunkcase) and is safe by construction: write-free, streamed to stdout, never touches the working tree, never creates or modifies a ref. Use it whenever the sub-skill needs SHA-pinned file content.gh:gh pr viewfor PR metadata,gh api graphqlfor reviews + comments. Notgh pr diff— it always emits current tip vs base with no way to pin a historical SHA, so it can't be used for pre-image or freshness checks (Step 6b covers this in detail); if the sub-skill needs SHA-pinned f