メニュー
Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Consult before delegating implementation when an approved plan benefits from worker context isolation and durable coordination.
Consult before attempting a fix when root cause or behavior is unclear, failures repeat, components interact, or guessing would be unsafe.
Consult before implementing an observable behavior change when a meaningful automated test seam exists; use proportional red-green evidence.
Consult directly matching task playbooks before substantial design, debugging, implementation, review, or completion work without forcing full workflow execution.
Consult before making a substantive completion claim; require current trustworthy evidence and semantic acceptance.
Consult when multi-round implementation, context compaction, or worker handoff requires a durable execution contract.
| name | receiving-code-review |
| description | Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation. |
Read feedback and verify it against code, requirements, and current behavior. Treat review comments as evidence to evaluate, not orders or a social exchange.
Clarify ambiguity only when it changes intent, coupling, or safety. Independent and clear items may proceed while a separate load-bearing question is resolved; do not turn unrelated fixes into a one-item ritual. For accepted findings, state the observed issue, chosen change, and validation.
Push back when evidence shows a conflict with contracts, compatibility, architecture, or real usage. Keep the response factual; gratitude style is not a workflow requirement.
