receiving-code-review

Verify code review feedback by understanding, evaluating, and checking it against the codebase's reality before implementation. This ensures suggestions are technically sound, align with YAGNI principles, and prevent unnecessary work or broken functionality.

Handle code review disagreements using reasoned pushback instead of performative agreement. Constructively argue against feedback when technically justified, ensuring you first validate the suggestion against the codebase and project goals before responding.

Implement code review suggestions through a structured pattern: understand, verify, evaluate, and implement each item individually. This structured approach ensures thoroughness and confirms that each change aligns with project goals and YAGNI principles.

When code review feedback is unclear, request clarification before proceeding. The process emphasizes understanding and technically verifying suggestions first, preventing unnecessary work caused by implementing ambiguous or incorrect external suggestions.

Pushback on code review suggestions when they violate YAGNI principles, lack technical soundness, or threaten existing code integrity. Technically verify the feedback against the codebase reality first to justify your refusal with concrete evidence.

Yes, apply YAGNI principles to reject code review feedback when suggestions introduce unnecessary features. The framework evaluates whether feedback aligns with project goals and technical requirements before implementation, preventing scope creep and maintaining code integrity.