receiving-code-review

Respond to code-review feedback using a six-step pattern: read, understand, verify, evaluate, respond, and implement. Process one item at a time to ensure technical accuracy and avoid misinterpretation.

For unclear code-review feedback, ask clarifying questions before proceeding. This prevents misinterpretation and ensures you fully understand the requested changes before implementation.

Push back on code-review comments using technical reasoning and escalation rules when necessary. Avoid performative agreement and rely on verified technical accuracy to justify your response.

For external reviewer feedback, verify impact, context, and compatibility before making changes. This ensures iterative changes are safe and technically accurate across different team environments.

After code review, follow a post-review validation order: verify each item, evaluate technical accuracy, respond, then implement one item at a time to maintain safe iterative changes.