代码审查接收指南：如何高效处理反馈、分类优先级与专业回应

receiving-code-reviews by doanchienthangdev/omgkit

1 周安装量

3 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/doanchienthangdev/omgkit --skill receiving-code-reviews

团队协作开发代码质量

🇨🇳中文介绍

接收代码审查

快速开始

暂停 - 在回应前阅读所有评论；不要立即做出反应
分类 - 按类型排序：阻塞性问题、建议、问题、细节挑剔、赞扬
优先级排序 - 首先处理阻塞性问题，然后是问题，接着是建议
回应 - 对每条评论都进行确认，并说明具体行动或理由
学习 - 追踪重复出现的反馈模式以改进

功能特性

功能	描述	指南
反馈分类	对评论类型进行分类	阻塞性问题 > 问题 > 建议 > 细节挑剔
回应模板	专业的回复模式	同意、有理由的反对、澄清、推迟
系统化处理	处理所有评论	将相关评论分组，发布总结更新
学习提炼	识别改进模式	追踪重复出现的类别
反模式	避免防御性回应	不争论、不忽视、不轻视
进度追踪

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

find-skills 技能搜索工具 - Vercel Labs 开源智能体技能包管理器

812,900 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

269,400 周安装

Vercel Web界面规范检查工具 - 自动检测代码是否符合Web设计指南

218,000 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

147,400 周安装

# 反馈类别优先级
1. blocking - 合并前必须修复
2. question - 回答问题以推进讨论
3. suggestion - 考虑并回应
4. nitpick - 如果容易就修复，否则讨论
5. praise - 感谢审查者
6. fyi - 确认收到

# 回应模板
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]"



# 处理流程
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!

应该做	应避免
在回应前阅读所有评论	立即/防御性地做出反应
按优先级分类（阻塞性问题优先）	不加解释地忽略评论
回应每一条评论	未处理就标记为已解决
具体化 - 引用提交哈希	对简单的改动过度解释
感谢审查者的见解	将反馈视为针对个人
需要时请求澄清	无休止地争论个人偏好
从重复出现的反馈中学习	轻率地忽视细节挑剔
完成后重新请求审查	延迟回应反馈

requesting-code-reviews - 如何请求有效的审查
finishing-development-branches - 完成 PR 准备
verifying-before-completion - 审查前验证
solving-problems - 建设性地处理棘手反馈

🇺🇸English

Receiving Code Reviews

Quick Start

Pause - Read all comments before responding; don't react immediately
Categorize - Sort by type: blocking, suggestion, question, nitpick, praise
Prioritize - Address blocking issues first, then questions, then suggestions
Respond - Acknowledge every comment with specific action or reasoning
Learn - Track recurring feedback patterns for improvement

Features

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

Common Patterns

# 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!

Best Practices

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

Related Skills

requesting-code-reviews - How to request effective reviews
finishing-development-branches - Complete PR preparation
verifying-before-completion - Pre-review verification
solving-problems - Handle tough feedback constructively

Weekly Installs

Repository

doanchienthangdev/omgkit

GitHub Stars

First Seen

1 day ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

zencoder1

amp1

cline1

openclaw1

opencode1

cursor1