receiving-code-review

Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation.

- Verify feedback against actual codebase behavior, test coverage, and architectural context before proceeding

- Ask for clarification on unclear items before implementing anything; partial understanding leads to wrong fixes

- Push back on suggestions that break functionality, lack context, violate YAGNI, or conflict with established decisions using technical reasoning

- Implement multi-item feedback in priority order (blocking issues first), testing each fix individually to catch regressions

- Acknowledge correct feedback through action and specific description of what changed, not gratitude expressions

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: