code-review
审查代码并管理 PR 反馈
متاح أيضًا من: EricDuMingTong,getsentry,21pounder,supercent-io,coderabbitai,davila7,ANcpLua,21pounder,DavidDworetzky,Cain96,Joseph OBrien,Joseph OBrien,Bind,Claude Assistant
该技能从两个视角简化代码审查流程。它提供用于创建高质量 PR 的模板，并给出建设性回应审查反馈的指南。
تنزيل ZIP المهارة
رفع في Claude
اذهب إلى Settings → Capabilities → Skills → Upload skill
فعّل وابدأ الاستخدام
اختبرها
استخدام "code-review". Review this authentication fix and help me respond to the feedback about adding rate limiting
النتيجة المتوقعة:
- Suggested response: Good catch on rate limiting. I have added basic protection in commit abc123. For production, we should add token bucket limiting - would you prefer I add that now or file a follow-up ticket?
استخدام "code-review". Help me write a PR description for a new database migration
النتيجة المتوقعة:
- What: Add user email verification column to users table
- Why: Required for upcoming email verification feature launch
- How: Added nullable email_verified_at column with migration file
- Testing: Migration tested locally, unit tests added for new column access
استخدام "code-review". Give feedback on this security-related PR
النتيجة المتوقعة:
- Must-fix: Input validation is missing for user_id parameter - could lead to injection
- Should-fix: Error messages reveal internal implementation details
- Could-fix: Variable naming could be more descriptive for auth flows
- Positive: Good test coverage on the authentication logic
التدقيق الأمني
آمنPure markdown documentation skill containing only PR templates, checklists, and response patterns. No executable code, file access, network calls, or command execution. All static findings are false positives from pattern matching without semantic understanding.
عوامل الخطر
🌐 الوصول إلى الشبكة (1)
📁 الوصول إلى نظام الملفات (1)
⚙️ الأوامر الخارجية (3)
درجة الجودة
ماذا يمكنك بناءه
创建高质量 PR
为审查者准备具有清晰上下文、测试确认和结构化描述的 pull request。
提供高质量反馈
给出建设性、优先级明确的反馈，包含清晰的 must/should/could 分类与积极认可。
标准化审查流程
通过共享模板和指南，在团队成员之间建立一致的代码审查模式。
جرّب هذه الموجهات
Review this code change. The PR description follows this template: What: [one-line summary], Why: [reason for change], How: [implementation approach], Testing: [test status]. Focus on bugs, edge cases, and clarity.
Help me respond to this reviewer feedback. The feedback type is [bug/style/design/opinion]. My original intent was [explanation]. Draft a response that is [accepting/explanatory/discussing].
Walk through this self-review checklist for my PR: tests pass, no lint errors, changes are focused, commit messages follow conventions, and context is clear. Point out any gaps.
Review this PR code. Structure feedback by priority: Must-fix (blocking issues), Should-fix (important problems), Could-fix (improvements). Include at least one positive observation.
أفضل الممارسات
- 保持 PR 小而精（少于 300 行）以加快审查
- 提供关于变更内容和原因的上下文
- 在请求他人反馈前先进行自我审查
- 使用优先级标签将阻塞问题与建议分开
تجنب
- 提交体量巨大且范围或上下文不清晰的 PR
- 对审查反馈作出防御性或轻视的回应
- 跳过自我审查，仅依赖自动化检查
- 忽视风格反馈且不遵循团队规范