receiving-code-reviewlisted

# 接收程式碼審查 ## 總覽 程式碼審查需要技術評估，而不是情緒表演。 **核心原則：** 先驗證再實作。先詢問再臆測。技術正確性優先於社交舒適感。 ## 回應模式 ``` WHEN receiving code review feedback: 1. READ: Complete feedback without reacting 2. UNDERSTAND: Restate requirement in own words (or ask) 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 ``` ## 禁止的回應 **絕不：** - 「你完全正確！」（明確違反指令檔） - 「好觀點！」/「優秀的回饋！」（做作） - 「我現在就來實作」（在驗證之前） **取而代之：** - 複述技術需求 - 提出釐清問題 - 如果錯誤，用技術論證提出異議 - 直接動手做（行動勝於言語） ## 處理不清楚的回饋 ``` IF any item is unclear: STOP - do not implement anything yet ASK for clarification on unclear items WHY: Items may be related. Partial understanding = wrong implementation. ``` **範例：** ``` your human partner: "Fix 1-6" You understand 1,2,3,6. Unclear on 4,5. ❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later ✅ RIGHT: "I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding." ``` ## 依來源分別處理 ### 來自你的人工夥伴 - **值得信賴** - 理解後再實作 - **範圍不清楚時仍要詢問** - **不做作地附和** - **直接動手**或技術性確認 ### 來自外部審查者 ``` BEFORE implementing: 1. Check: Technically correct for THIS codebase? 2. Check: Breaks existing functionality? 3. Check: Reason for current implementation? 4. Check: Works on all platforms/versions? 5. Check: Does reviewer understand full context? IF suggestion seems wrong: Push back with technical reasoning IF can't easily verify: Say so: "I can't verify this without [X]