receiving-code-review

Process code review feedback through a structured six-step workflow: READ the comment, UNDERSTAND its intent, VERIFY it against your codebase, EVALUATE whether it's correct, RESPOND with either implementation or technical pushback, and IMPLEMENT the change or document your reasoning. This disciplined approach prevents misinterpretation and ensures technical correctness.

Stop and ask for clarification before implementing. The clarification protocol prevents wasted effort on incorrect interpretations. Request specific examples, context about architectural concerns, or details about edge cases the reviewer encountered to ensure you understand the feedback accurately.

Yes. Push back with technical reasoning when suggestions lack full context, violate architectural decisions, or are incorrect. Document your counter-arguments with evidence from the codebase, design decisions, or performance implications to support your position non-emotionally.

Verify each comment against your codebase before responding, evaluate whether the suggestion aligns with existing patterns, write unit tests for changes, and maintain traceability by documenting test coverage. This risk-aware validation prevents introducing bugs through code review implementations.

Apply the structured workflow to each comment independently: understand the context, verify applicability, evaluate correctness, then respond or implement. This systematic approach manages multi-item feedback efficiently and prevents bundling unrelated concerns.

Frame responses around technical facts, codebase evidence, and architectural reasoning rather than personal preference. Use the six-step workflow to separate emotional reaction from technical evaluation, enabling professional disagreement and collaborative problem-solving.