receiving-code-review

To handle unclear code review feedback, pause and request clarification before proceeding. This prevents wrong implementations by ensuring you fully understand the requirement and can verify it against the codebase.

The best way to push back on questionable code review comments is to verify the feedback against the codebase reality, evaluate its technical correctness, and then respond with clear technical reasoning.

To implement code review feedback safely, apply changes one item at a time and run tests after each implementation. This disciplined approach ensures technical accuracy and prevents partial or wrong implementations.

To verify technical accuracy when receiving a pull request review, read the feedback in full, restate the requirement, and evaluate it against the current codebase reality before implementing any changes.

To process code review comments effectively, follow a six-step pattern: read the feedback, understand the requirement, verify against the codebase, evaluate technical correctness, respond with rationale, and implement with tests.

Verifying code review feedback against the codebase before implementing ensures that the requested changes are technically sound and prevents incorrect modifications based on outdated or questionable reviewer assumptions.