メニュー
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 ページを確認してインストールできます。
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.
SOC 職業分類に基づく
| 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.