菜单
Use when handling received code-review feedback on a PR or diff, including requested changes, inline comments, approvals, non-blocking notes, and disputed suggestions. Separates accepted fixes, refutations, deferrals, clarification needs, and merge handoff.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | receiving-code-review |
| description | Use when handling received code-review feedback on a PR or diff, including requested changes, inline comments, approvals, non-blocking notes, and disputed suggestions. Separates accepted fixes, refutations, deferrals, clarification needs, and merge handoff. |
| metadata | {"short-description":"Process review feedback safely"} |
Use this skill to process review feedback without blindly applying every suggestion.
Each comment needs a disposition, evidence, and either a smallest safe fix or a clear reason no code change is made.
Read review state from the source of truth.
Assign each item exactly one disposition:
accept: The reviewer identified a real issue in scope.refute: The suggestion conflicts with requirements, evidence, or scope.defer: The issue is valid but belongs outside this PR.clarify: The requested change is ambiguous or lacks enough location or
acceptance detail.acknowledge: The item is informational, approval-only, or already
satisfied.Apply accepted fixes with the smallest safe change.
Respond with evidence.
Hand off approvals to branch-completion.
Approve,
as an approval signal.Use this compact ledger when review has more than one item:
| Comment / thread | Disposition | Action | Evidence |
|---|---|---|---|
<id or location> | accept/refute/defer/clarify/acknowledge | <fix or response> | <test, requirement, scope, or code ref> |
If the ledger has only approval and no required changes, record the approval
signal and move to branch-completion.
Use when finishing a branch or PR after verification and review, including merge, PR publication, keep, discard, cleanup, local sync, and reporting merge or PR URLs with current git state.
Use when preparing a focused code-review request for a PR or diff after implementation evidence exists, especially to package scope, reviewer focus, PR URL, verification, known risks, and deferred work without deciding final submit readiness.
Use before every submission to decide whether required checks, artifacts, and branch evidence are complete enough to submit.
Use when work is complex, long-running, multi-step, cross-boundary, likely to span multiple PRs/sessions, or needs handoff-ready planning under plans/.
Use when adding or changing Agent-facing workflows, generated prompts, collect plans, executable handoff artifacts, CLI workflows, controller/target-local workflow chains, or validation artifacts consumed by downstream reports. Do not use for ordinary code changes without an Agent-facing workflow or generated instruction surface.
Use when fixing or investigating crashes, regressions, flakes, hangs, incorrect outputs, or incidents.