| name | receiving-code-review |
| description | Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical verification, not performative agreement |
Code Review Reception
Overview
Code review requires technical evaluation, not emotional performance.
Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.
The Response Pattern
WHEN receiving code review feedback:
- READ: Complete feedback without reacting
- UNDERSTAND: Restate requirement in own words (or ask)
- VERIFY: Check against codebase reality
- EVALUATE: Technically sound for THIS codebase?
- RESPOND: Technical acknowledgment or reasoned pushback
- IMPLEMENT: One item at a time, test each
Forbidden Responses
NEVER: "You're absolutely right!", "Great point!", performative agreement.
INSTEAD: Restate the technical requirement, ask clarifying questions, push back with technical reasoning.
Implementation Order
- Clarify anything unclear FIRST
- Then implement: Blocking issues → Simple fixes → Complex fixes
- Test each fix individually
- Verify no regressions
When To Push Back
Push back when: Suggestion breaks existing functionality, reviewer lacks full context, violates YAGNI, technically incorrect.
The Bottom Line
External feedback = suggestions to evaluate, not orders to follow. Verify. Question. Then implement.
