flow-receiving-reviewlisted

# Flow Receiving Review - 处理代码审查反馈 ## The Iron Law ``` VERIFY FEEDBACK BEFORE IMPLEMENTING - DON'T BLINDLY AGREE ``` ## Overview When receiving code review feedback, maintain technical rigor. Reviewers can be wrong. Your job is to: 1. Understand the feedback 2. Verify it's correct 3. Then implement (or push back) ## The Process ### Step 1: Understand the Feedback ```yaml For each comment: 1. Read completely - don't skim 2. Identify the concern: - Is it a bug? - Is it a style preference? - Is it a performance issue? - Is it a security concern? 3. If unclear → ASK for clarification - "Could you elaborate on why X is problematic?" - "What specific scenario does this address?" ``` ### Step 2: Verify the Feedback ```yaml Before implementing ANY change: 1. Is the feedback technically correct? - Does the suggested change actually fix the issue? - Could it introduce new problems? 2. Does it align with project standards? - Check Constitution - Check existing patterns 3. Is there evidence? - Can you reproduce the issue? - Does the suggested fix work? If feedback seems wrong: → Don't silently disagree → Don't blindly implement → Respond with your analysis ``` ### Step 3: Respond Appropriately ```yaml If feedback is correct: → Acknowledge: "Good catch, fixing now" → Implement the fix → Verify the fix works If feedback is unclear: → Ask: "Could you clarify what you mean by X?" → Don't gu