Agent skill · writing content · aiskillstore
flow-receiving-review
Handle code review feedback with technical rigor. Don't blindly agree - verify before implementing.
Why this skill is useful
Codifies a structured approach to handling code review feedback, ensuring technical rigor and preventing blind compliance.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Flow Receiving Review - 处理代码审查反馈 The Iron Law 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 Step 2: Verify the Feedback Step 3: Respond Appropriately Rationalization Prevention Excuse Reality -------- --------- "Reviewer knows better" Reviewers make mistakes. Verify. "Just do what they say" Blind compliance = poor code. "Don't want to argue" Technical discussion ≠ argument. "It's faster to just change it" Wrong changes waste more time. "They'll reject if I push back" Good reviewers appreciate rigor. Red Flags - STOP If you find yourself: Implementing changes you don't understand Agreeing with feedback you think is wrong Not asking clarifying questions Making changes without verifying they work STOP. Understand first. Verify second. Implement third. Response Templates Agreeing with Feedback Asking for Clarification Respectfully Disagreeing Requesting Evidence Integration with flow-review This skill is used in /flow-review when processing reviewer feedback: Cross-Reference flow-review.md - Two-stage review command spec-reviewer.md - Spec compliance agent code-quality-reviewer.md - Quality review agent --- [PROTOCOL]: 变更时更新此头部，然后检查 CLAUDE.md
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/flow-receiving-review