receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative

定位

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

核心流程/章节

• Overview
• The Response Pattern
• Forbidden Responses
• Handling Unclear Feedback
• Source-Specific Handling
• YAGNI Check for "Professional" Features
• Implementation Order
• When To Push Back

原文要点

Code Review Reception

Overview

Code review requires technical evaluation, not emotional performance.

Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.

The Response Pattern

WHEN receiving code review feedback:

1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3....

## 适用场景

- 基于 description 推断：Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires 

## 参见

- GitHub: [superpowers](https://github.com/obra/superpowers)