receiving-code-review

Code review feedback should be verified against the codebase and project standards before implementation. You must restate the requirement, verify the issue, evaluate the technical context, and implement changes one item at a time with traceable reasoning.

Pushback on a pull request review comment requires structured technical justification. You should verify the feedback against tests and codebase logic first, then respond with clear technical reasoning if the feedback is incorrect or ambiguous.

Process multiple code review items by reading all feedback in full, restating each requirement to avoid ambiguity, and implementing changes one item at a time. This ensures traceable reasoning and testing for each individual change.

You should ask for clarification during a code review when feedback items are ambiguous. Restate the requirement in your own words to verify understanding, and request clarifications before proceeding with any code changes.

To stop performative agreement, enforce a strict workflow for code review feedback: read, understand, verify, evaluate, respond, and implement. Disallow performative agreement by requiring technical verification against the codebase before agreeing to changes.