receiving-code-review

Handle ambiguous code review feedback by restating the requirements in your own words and asking precise questions to clarify technical uncertainties before implementing any changes. This approach enforces technical rigor, preventing performative agreement and ensuring you fully understand the requested modifications before altering the codebase.

The best way to verify a code review suggestion is to check the actual codebase, existing tests, and dependencies to confirm feasibility. Evaluating the suggestion against codebase reality ensures technical safety and validates whether the proposed change aligns with the system's current constraints.

Push back on technically unsafe code review comments by communicating technical constraints and providing reasoned arguments for why the suggestion is unsafe. Verify the issue against the repository first, then respond with clear technical evidence rather than performative agreement or premature changes.

Implement multiple items from code review feedback one at a time, validating each change with focused tests before moving to the next. This step-by-step process enforces a sequence of reading, understanding, verifying, evaluating, responding, and implementing to maintain code quality and technical rigor.

You should restate requirements before implementing code review suggestions whenever the feedback is unclear or potentially technically questionable. Restating the requirement in your own words ensures you verify against codebase reality and avoid premature changes driven by misunderstandings or ambiguous instructions.