handle-review

To verify code review feedback before implementation, follow a structured 6-step response pattern that prioritizes understanding, technical verification, and reasoned pushback over performative agreement. This ensures technical accuracy and prevents errors.

Blindly accepting code review feedback causes problems by introducing new bugs or removing necessary functionality. It skips technical verification, leading to errors and degrading overall code quality in the project.

Handling feedback from external reviewers versus human partners requires distinguishing the feedback sources. The process applies specific verification steps for each source to ensure adherence to project requirements and technical correctness.

You can push back on code review suggestions if they are technically incorrect. The process enforces reasoned pushback over performative agreement, prompting you to verify technical soundness and codebase impact before making modifications.

The best way to manage code review feedback for technical rigor is applying a strict verification process before implementation. This prevents performative agreement and ensures all suggested changes align with project requirements.

You should not use performative agreement during code review when receiving feedback from human partners or external reviewers. Instead, prioritize understanding and verification to maintain technical accuracy and codebase integrity.