菜单
Independently review a defined change before integration when requested or when material security, data, concurrency, migration, contract, or cross-module risk warrants it; exclude incoming feedback.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute an existing plan when implementation is authorized and dependent outcomes need tracking; skip short routine checklists.
Mandatory newcomer-safe router for every conversation. Classify by action, impact, and named risk; add workflows only when their descriptions match.
Create a durable plan when explicitly requested, required by the High-risk tier, or needed for resumable dependency coordination; skip routine native planning.
Resolve ambiguous product or system work before implementation. Use when materially different interpretations would change scope, architecture, or consequential outcomes; skip precise tasks.
Complete an authorized commit, push, integration, PR, branch, or worktree action while preserving user state. Use after relevant verification when the user or repository requires delivery.
Evaluate incoming code-review feedback against repository evidence. Keep evaluation-only requests read-only; implement supported fixes only when authorized.
| name | requesting-code-review |
| description | Independently review a defined change before integration when requested or when material security, data, concurrency, migration, contract, or cross-module risk warrants it; exclude incoming feedback. |
Do not use this workflow merely to evaluate incoming reviewer feedback.
HEAD~1 covers the work.Keep the review read-only. Report actionable findings by severity with file and line evidence, impact, and a concrete fix. Omit strengths, generic recommendations, and findings that do not change the decision.
Block integration on supported Critical and Important findings. Re-review only when a substantial correction changes the risk surface; otherwise run the affected verification directly.