nobody-receives-code-review

Evaluate code review feedback by technically verifying each concern against the actual codebase to ensure it is necessary and correct. This approach prevents performative agreement and guides you to respond with clear evidence rather than blindly applying suggested changes.

Respond to code review disagreements with evidence-based replies that technically verify the concern and justify your position. This ensures software correctness and prevents blind changes by validating whether the proposed solution is actually sound for your workflow.

Verify code review suggestions to prevent introducing new issues and ensure changes are actually necessary for software development. Blindly accepting feedback without technical verification can compromise code quality and correctness in the long run.

Systematically check reviewer feedback by prompting yourself to technically verify each piece of feedback received and validating the proposed solution. This critical evaluation ensures changes maintain code quality and correctness without performative agreement.

Use this critical evaluation process in any software development workflow where code quality and correctness are paramount. It applies broadly to scenarios where reviewers suggest changes and you need to technically verify concerns before implementation.

Do not apply code review feedback directly when the suggestion lacks technical verification or evidence to support its necessity. Prevent performative agreement by systematically checking if the feedback is valid and if the proposed solution is sound.