receiving-code-review

Verify code review feedback by technically evaluating it against the codebase's reality to ensure correctness and project alignment. Apply technical rigor and YAGNI principles to question feedback before committing to implementation.

Handle pull request feedback by verifying its necessity and impact on the current codebase before implementation. Prioritize technical correctness over performative agreement to prevent blind acceptance of incorrect changes.

Evaluating architectural changes is needed to ensure alignment with project goals and technical constraints. Verifying feedback prevents unnecessary modifications and maintains technical rigor when receiving external suggestions.

Yes, this approach applies to scenarios involving feedback from both human partners and external reviewers. It provides a structured pattern for understanding, verifying, and responding to feedback.

Blindly accepting feedback risks implementing potentially incorrect or unnecessary changes. This Skill emphasizes verification before implementation, requiring adherence to technical rigor and YAGNI principles to avoid performative agreement.

Structure your response by following a clear pattern for understanding, verifying, and responding to feedback. This ensures clear communication and prioritizes technical correctness over performative agreement during the developer workflow.