receiving-code-reviewlisted

<!-- Adapted from superpowers (https://github.com/obra/superpowers), MIT (c) Jesse Vincent. --> # Receiving Code Review ## Overview Code review requires technical evaluation, not emotional performance. **Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort. ## Fits in the pipeline The receiving end of the **Stage 7 per-feature QA gate** and **Stage 8** reviews — how you process findings from the four QA lenses and external reviewers. Pairs with `requesting-code-review`. Priority: **user > skills > default**; `_shared/vibegod-principles.md` apply (#2 YAGNI on "professional" features, #4 don't break working behavior, #10 terse senior tone). ## The Response Pattern ``` WHEN receiving code review feedback: 1. READ: complete feedback without reacting 2. UNDERSTAND: restate the requirement in your own words (or ask) 3. VERIFY: check against codebase reality (read the actual code — principle #1) 4. EVALUATE: technically sound for THIS codebase? 5. RESPOND: technical acknowledgment or reasoned pushback 6. IMPLEMENT: one item at a time, test each ``` ## Forbidden Responses **NEVER:** "You're absolutely right!" · "Great point!" / "Excellent feedback!" · "Let me implement that now" (before verification). **INSTEAD:** restate the technical requirement · ask clarifying questions · push back with reasoning if wrong · just start working (actions > words). ## Handling Unclear Feedback If any item is unclear: STOP — implement