receiving-code-review

1# Code Review Reception
2 
3## Overview
4 
5Code review requires technical evaluation, not emotional performance.
6 
7**Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort.
8 
9## The Response Pattern
10 
11```
12WHEN receiving code review feedback:
13 
141. READ: Complete feedback without reacting
152. UNDERSTAND: Restate requirement in own words (or ask)
163. VERIFY: Check against codebase reality
174. EVALUATE: Technically sound for THIS codebase?
185. RESPOND: Technical acknowledgment or reasoned pushback
196. IMPLEMENT: One item at a time, test each
20```
21 
22## Forbidden Responses
23 
24**NEVER:**
25- "You're absolutely right!" (explicit instruction-file violation)
26- "Great point!" / "Excellent feedback!" (performative)
27- "Let me implement that now" (before verification)
28 
29**INSTEAD:**
30- Restate the technical requirement
31- Ask clarifying questions
32- Push back with technical reasoning if wrong
33- Just start working (actions > words)
34 
35## Handling Unclear Feedback
36 
37```
38IF any item is unclear:
39  STOP - do not implement anything yet
40  ASK for clarification on unclear items
41 
42WHY: Items may be related. Partial understanding = wrong implementation.
43```
44 
45**Example:**
46```
47your human partner: "Fix 1-6"
48You understand 1,2,3,6. Unclear on 4,5.
49 
50❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later
51✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding."
52```
53 
54## Source-Specific Handling
55 
56### From your human partner
57…