| name | receiving-code-review |
| description | Consult after receiving review feedback and before implementation when the feedback needs evidence-based evaluation. |
Receiving Code Review
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.