菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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 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.
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.
| name | requesting-code-review |
| description | 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. |
| metadata | {"short-description":"Prepare focused review requests"} |
Use this skill to ask for review with enough context for a reviewer to make a decision quickly.
The skill packages review context. It does not decide submit readiness, replace
quality-gate, or hide known gaps.
quality-gate owns submit/no-submit readiness.requesting-code-review owns the review request package.receiving-code-review owns review feedback handling after comments arrive.branch-completion owns post-review branch and PR lifecycle actions.Confirm the review target.
Gather evidence.
State reviewer focus.
Send a review request that includes:
Review target: <raw PR URL or diff>
Scope:
- <what changed>
- <what did not change>
Verification:
- `<command>`: <result>
Reviewer focus:
- <boundary, behavior, generated artifact, or risk to inspect>
Known risks / deferred:
- <risk or none>
Please leave review comments on: <GitHub PR / specified channel>