Skip to content
cccskills
FreePublished on GitHub

requesting-code-review

Organizes a code review by giving a reviewer subagent the requirements, a change summary, and the relevant Git commits. It helps check completed work and handle findings by severity before continuing or merging.

OriginalShow the original description

完成任务、实现重要功能或合并前使用,用于验证工作成果是否符合要求

See how to install

Good for

  • Review a completed development task
  • Check a major feature against its requirements
  • Request a code review before merging into main
  • Get another perspective on a difficult bug fix

Files included (2)

  • SKILL.md2.9 KB
  • code-reviewer.md6.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

请求代码审查

派遣代码审查子代理,在问题扩散之前发现它们。审查者获得的是精心组织的评估上下文——绝不是你的会话历史。

核心原则: 早审查,勤审查。

何时请求审查

必须审查:

  • 子代理驱动开发中每个任务完成后
  • 完成重要功能后
  • 合并到 main 之前

可选但有价值:

  • 卡住时(换个视角)
  • 重构之前(建立基线)
  • 修复复杂 bug 之后

如何请求

1. 获取 git SHA:

BASE_SHA=$(git rev-parse HEAD~1)  # 或:git merge-base origin/main HEAD
HEAD_SHA=$(git rev-parse HEAD)

2. 派遣代码审查子代理:

使用 Task 工具,指定 general-purpose 类型,填写 code-reviewer.md 中的模板

占位符说明:

  • {DESCRIPTION} - 你刚完成的内容简要说明
  • {PLAN_OR_REQUIREMENTS} - 预期功能
  • {BASE_SHA} - 起始提交
  • {HEAD_SHA} - 结束提交

3. 处理反馈:

  • Critical 问题立即修复
  • Important 问题在继续之前修复
  • Minor 问题记录下来稍后处理
  • 如果审查者有误,用技术理由反驳

示例

[刚完成任务 2:添加验证功能]

你:让我在继续之前请求代码审查。

BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | cut -d' ' -f1)
HEAD_SHA=$(git rev-parse HEAD)

[派遣代码审查子代理]
  DESCRIPTION: 添加了 verifyIndex() 和 repairIndex(),支持 4 种问题类型
  PLAN_OR_REQUIREMENTS: docs/superpowers/plans/deployment-plan.md 中的任务 2
  BASE_SHA: a7981ec
  HEAD_SHA: 3df7661

[子代理返回]:
  优点:架构清晰,测试真实
  问题:
    Important:缺少进度指示器
    Minor:报告间隔使用了魔法数字 (100)
  评估:可以继续

你:[修复进度指示器]
[继续任务 3]

常见的合理化借口

借口现实
"我自己看一下 diff 就行了,不用专门派审查者"你是协调者——在自己的会话里读 diff 会烧掉你继续推进工作所需的上下文窗口。派一个审查子智能体:diff 和评估过程都待在它的上下文里,只有结论回到你这里。
"审查者需要我的全部会话历史才能理解这次改动"给它精心组织的上下文,绝不给会话历史。这样审查者才会盯着工作成果,而不是你的思考过程。

红线

绝不要:

  • 因为"很简单"就跳过审查
  • 忽略 Critical 问题
  • 带着未修复的 Important 问题继续推进
  • 对合理的技术反馈进行争辩

如果审查者有误:

  • 用技术理由反驳
  • 展示证明其可行的代码/测试
  • 要求澄清

参见模板:requesting-code-review/code-reviewer.md

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

brainstorming

FreeSummary

Turn development ideas into agreed designs through focused conversation. The skill clarifies goals, constraints, and success criteria, then chooses a process for feasibility research, small changes, or new systems before implementation begins.

  • Clarifying the purpose of a new feature
  • Agreeing on a design for an existing code change
  • Comparing approaches for a new system
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

Write Chinese code review feedback that clearly distinguishes required fixes, suggestions, and optional advice. Use question and suggestion templates, organize review summaries, and follow guidance for mixed Chinese-English comments and commit messages.

  • Writing Chinese review comments with clear priorities
  • Rephrasing blunt feedback as questions or suggestions
  • Standardizing Chinese-English comments and commit messages
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.

  • Standardizing Chinese commit messages across a team
  • Checking commit formats with commitlint and husky
  • Generating changelogs with Chinese section headings
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

Write and revise Chinese technical documentation using consistent spacing, punctuation, terminology, and structure. Includes README.md and API documentation templates, bilingual formatting examples, and a checklist for reviewing documents before publication.

  • Standardizing spacing and punctuation in Chinese documents
  • Writing a Chinese README.md
  • Organizing API documentation in Chinese and English
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

Set up Git workflows for Gitee, Coding.net, 极狐 GitLab, and CNB with platform-specific connection and authentication examples. Choose branching rules, standardize Chinese commit messages, and adapt automated testing and deployment configurations to your team's workflow.

  • Configure connections and authentication for Chinese Git platforms
  • Choose branching rules that fit the team
  • Standardize Chinese commit messages and review templates
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

Review AI agent session logs to document repeated work, departures from plans, delays, and token usage. Produce an evidence-based report with file and line references, and prepare a bug report when appropriate.

  • Investigating delays or token usage in a session
  • Reviewing repeated work or departures from a plan
  • Checking whether a skill was activated
jnMetaCode/superpowers-zh8.3KUpdated Oct 17, 2026

See all skills by jnMetaCode

Report a problem with this skill