菜单
AI agent handles code review feedback professionally by categorizing, responding appropriately, and extracting learnings. Use when PR feedback arrives, addressing reviewer comments, or improving from feedback.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/doanchienthangdev/omgkit --skill receiving-code-reviews命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Automatic design system context injection for UI consistency
AI agent practices test-first development with the Red-Green-Refactor cycle for confident, well-designed code. Use when implementing features, fixing bugs, or establishing testing practices.
The agent enforces mandatory test completion before any task or feature can be marked as done, ensuring code quality through strict validation gates and evidence-based completion criteria.
基于 SOC 职业分类
正在显示 SKILL.md
| name | receiving-code-reviews |
| description | AI agent handles code review feedback professionally by categorizing, responding appropriately, and extracting learnings. Use when PR feedback arrives, addressing reviewer comments, or improving from feedback. |
| Feature | Description | Guide |
|---|---|---|
| Feedback Categories | Classify comment types | Blocking > Question > Suggestion > Nitpick |
| Response Templates | Professional reply patterns | Agree, disagree-with-reason, clarify, defer |
| Systematic Processing | Address all comments | Group related, post summary update |
| Learning Extraction | Identify improvement patterns | Track recurring categories |
| Anti-Patterns | Avoid defensive responses | No arguing, ignoring, or dismissiveness |
| Progress Tracking | Communicate resolution status | Addressed X, Discussing Y, Deferred Z |
# Feedback Category Priority
1. blocking - Must fix before merge
2. question - Answer to unblock discussion
3. suggestion - Consider and respond
4. nitpick - Fix if easy, discuss if not
5. praise - Thank the reviewer
6. fyi - Acknowledge
# Response Templates
AGREE:
"Good catch! Fixed in abc123."
DISAGREE (with reason):
"I considered this approach but chose current because:
- [reason 1]
- [reason 2]
What do you think given these trade-offs?"
CLARIFY:
"Could you elaborate on [point]? Want to understand fully."
DEFER:
"Good idea! Outside PR scope - created follow-up: [link]"
# Processing Workflow
1. Read ALL comments first (don't start responding)
2. Categorize and sort by priority
3. Group related comments together
4. Address blocking issues first
5. Answer questions to unblock
6. Consider suggestions thoughtfully
7. Post summary update:
## Review Response Summary
- Addressed: 8 comments
- Pending discussion: 2 comments
- Deferred (follow-up issues): 1 comment
Ready for another look!
| Do | Avoid |
|---|---|
| Read all comments before responding | Reacting immediately/defensively |
| Categorize by priority (blocking first) | Ignoring comments without explanation |
| Respond to every comment | Marking resolved without addressing |
| Be specific - reference commit hashes | Over-explaining simple changes |
| Thank reviewers for insights | Taking feedback personally |
| Ask for clarification when needed | Arguing about preferences endlessly |
| Learn from recurring feedback | Dismissing nitpicks dismissively |
| Re-request review when done | Delaying response to feedback |
requesting-code-reviews - How to request effective reviewsfinishing-development-branches - Complete PR preparationverifying-before-completion - Pre-review verificationsolving-problems - Handle tough feedback constructively