receiving-code-reviewlisted

# Receiving Code Review ## Contents - [Overview](#overview) - [Response Pattern](#response-pattern) - [Forbidden Responses](#forbidden-responses) - [Handling Ambiguous Feedback](#handling-ambiguous-feedback) - [Handling by Source](#handling-by-source) - [From the User](#from-the-user) - [From an External Reviewer](#from-an-external-reviewer) - [YAGNI (You Aren't Gonna Need It) Check for "Professional" Features](#yagni-you-arent-gonna-need-it-check-for-professional-features) - [Implementation Order](#implementation-order) - [When to Rebut](#when-to-rebut) - [Acknowledging Correct Feedback](#acknowledging-correct-feedback) - [Gracefully Correcting a Rebuttal](#gracefully-correcting-a-rebuttal) - [Common Mistakes](#common-mistakes) - [Examples](#examples) - [Replying on a GitHub Thread](#replying-on-a-github-thread) - [Conclusion](#conclusion) ## Overview A code review demands technical evaluation, not an emotional performance. ○ Core principles - Verify before implementing. - Ask before assuming. - Technical accuracy over social comfort. ## Response Pattern ``` When you receive code review feedback: 1. Read: read all the feedback without reacting 2. Understand: restate the requirement in your own words (or ask) 3. Verify: check it against the reality of the codebase 4. Evaluate: is it technically sound for this codebase? 5. Respond: technical acknowledgment or a grounded rebuttal 6. Implement: one item at a time, testing each one ``` ## Forbidden Responses □ Neve