receiving-code-review

Handle code review feedback by verifying the suggestion against the actual codebase and tests before implementing. Respond with reasoned pushback using concrete technical reasoning and code references instead of performative agreement.

The best way to verify a code review suggestion is to restate the requirement, check it against repository constraints, and evaluate technical soundness. Outline an itemized plan to implement changes one step at a time for measurable validation.

Push back on a code review comment by providing concrete reasoning and direct references to existing code and tests. Ensure your technical evaluation prioritizes correctness over social comfort and avoids emotional performance.

Implement code review changes safely by limiting the scope to a single change per step. Outline a technically sound, itemized plan and test each increment individually to minimize risk and ensure measurable validation.

Restate code review requirements in your own words to preserve objectivity and avoid misinterpretation. If a suggestion is unclear, ask for clarification before reacting to ensure the requested change is technically sound for your codebase.

Ask for clarification during a code review when feedback is ambiguous or cannot be verified against project constraints. Read the feedback completely before reacting to ensure you evaluate whether the requested change is technically sound for the current context.