receiving-code-review

Evaluate code review feedback by systematically verifying suggestions against your codebase and technical correctness. Apply a structured 6-step pattern—READ, UNDERSTAND, VERIFY, EVALUATE, RESPOND, IMPLEMENT—processing one item at a time, testing each change, and documenting decisions to maintain traceability and prevent blind implementation of unclear or incorrect suggestions.

Push back on code review feedback when suggestions are technically questionable, unclear, or lack justification. Provide reasoned technical arguments grounded in your codebase reality rather than accepting feedback performatively. This prevents unnecessary changes, maintains code quality, and ensures only valid improvements are integrated.

Stop and request clarification before implementing any unclear feedback. A clarification protocol ensures you fully understand the reviewer's intent and technical reasoning. This prevents wasted effort, avoids introducing bugs, and creates a shared understanding of the required changes.

Verify feedback by checking suggestions directly against your codebase state, existing patterns, and technical requirements. Compare the proposed change against current implementation to confirm correctness. This verification step prevents implementing incorrect suggestions and identifies cases where feedback conflicts with your architecture or constraints.

Document decisions during code review processing to create traceability, justify why changes were or were not implemented, and build institutional knowledge. Documentation helps future maintainers understand the reasoning behind code, supports team learning, and provides evidence for technical decisions made during review cycles.