/receiving-code-review
Code Review Reception
Process review feedback with technical rigor. No "you're absolutely right" reflex. Verify, push back, or act.
Used by 1 agent
What it does
Review reception as engineering, not performance. Read the full feedback before reacting, restate each item to confirm understanding, verify against the actual codebase, then respond with a technical acknowledgment or a reasoned pushback. One item at a time, tested per change. Unclear items block the whole batch until clarified.
Use it any time a reviewer (human or agent) returns notes. Especially critical when the feedback sounds wrong, when you're tired and tempted to just comply, or when partial understanding would produce the wrong implementation.
Outputs a structured response per item: accept with rationale, push back with technical reasoning, or ask for clarification. No performative agreement, no blanket "let me implement that." Pairs with `requesting-code-review` (the upstream dispatch) and `verification-before-completion` (the proof step after each fix).