receiving-code-review

# Code Review Reception ## Overview Code review requires technical evaluation, not emotional performance. Verify before implementing. Ask before assuming. **Core principle:** Verify before implementing. ## Response Pattern 1. READ - Complete feedback without reacting 2. UNDERSTAND - Restate requirement in own words 3. VERIFY - Check against codebase reality 4. EVALUATE - Technically sound for THIS codebase? 5. RESPOND - Technical acknowledgment or reasoned pushback 6. IMPLEMENT - One item at a time, test each ## When to Push Back - Suggestion breaks existing functionality - Reviewer lacks full context - Violates YAGNI - Conflicts with architectural decisions ## Tool Use Referenced by implementation processes when handling review feedback.