receiving-code-review

To verify code review feedback, read the comments, check them against your codebase architecture, and evaluate technical fit. You must confirm facts and ensure compatibility before writing any code to prevent context-mismatched or incorrect changes.

When code review comments are unclear, stop implementation immediately and ask targeted clarification questions. Do not guess or blindly implement changes; wait for explicit confirmation on ambiguous items before proceeding with any code modifications.

For external code review feedback, apply skeptical handling by checking scope, platform version impact, and reviewer understanding. Push back with technical reasoning if suggestions conflict with existing architecture or constraints before implementing anything.

Apply YAGNI checks to code review suggestions when asked to implement features properly; search the codebase for real usage first. If the suggested feature is unused, enforce YAGNI to avoid adding unnecessary code complexity.

To implement multi-item code review feedback incrementally, validate each item technically first, then implement one item at a time. Follow a strict test-by-test approach, verifying each change against the codebase before moving to the next.

Avoid performative agreement in code review responses because praise-like acknowledgments and blind implementation ignore unconfirmed facts. Respond with technical reasoning instead to ensure feedback is correct and applicable to your specific context.