receiving-code-review

Handle code review feedback using a disciplined verification workflow that enforces reading, understanding, and verifying comments against the codebase before implementing changes. This prevents blind agreement and ensures technical correctness through reasoned pushback.

Verify technical soundness by evaluating each review item against the actual codebase, assessing correctness, and providing reasoned pushback with rationale when needed. This verification step ensures feedback is technically valid before implementation.

Implement multiple code review changes incrementally, testing one item at a time to minimize risk and regressions. This staged implementation approach ensures each fix is verified independently before moving to the next feedback item.

When code review comments are unclear, request clarifications before proceeding with implementation. The verification workflow includes reading and understanding feedback items, requiring clarification when needed to ensure accurate and precise fixes.

Yes, you can and should push back on code review feedback when technically justified. The workflow involves evaluating technical soundness and responding with rationale, ensuring disagreements are backed by verified codebase analysis rather than emotional reactions.

Resolve code review feedback systematically through a six-step workflow: read, understand, verify against the codebase, evaluate technical soundness, respond with rationale, and implement items incrementally. This ensures disciplined handling of each feedback item.