requesting-code-review

requesting-code-review is a skill for Claude Code, Codex from jnMetaCode/superpowers-zh. It costs 24 tokens per session (844 once invoked), scanned A, original, MIT.

A code-review procedure for checking completed work against its requirements before it spreads or is merged. A code reviewer is a person or agent who looks for defects and missing parts.

In plain words
What is it for?
Reviewing finished tasks, major features, refactors, complex bug fixes, and changes prepared for the main branch.
Why use it?
It adds an independent check after important changes, so problems are found before merging and are ranked by urgency.

Skill for Claude CodeCodex

Part of the superpowers-zh plugin — 20 skills, 1 hook shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jnmetacode/superpowers-zh/requesting-code-review
Any agent
npx skills add jnMetaCode/superpowers-zh --skill requesting-code-review
Clone the repo
git clone --depth 1 https://github.com/jnMetaCode/superpowers-zh

Made for: Claude Code, Codex.

Or install superpowers-zh, the plugin that ships this one along with the rest of its 20 skills, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for requesting-code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/jnmetacode/superpowers-zh/requesting-code-review.svg)](https://agentmods.dev/skills/jnmetacode/superpowers-zh/requesting-code-review)
Your own site
<a href="https://agentmods.dev/skills/jnmetacode/superpowers-zh/requesting-code-review"><img src="https://agentmods.dev/badge/skills/jnmetacode/superpowers-zh/requesting-code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 844 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00844
Opus 5 $0.00012 $0.00422
Sonnet 5 $0.00005 $0.00169
Haiku 4.5 $0.00002 $0.00084

Measured 4d ago against content hash 4629ab5686d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requesting-code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/requesting-code-review/SKILL.md · 101 lines

What it actually says

请求代码审查

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

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

何时请求审查

必须审查:

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

可选但有价值:

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

如何请求

1. 获取 git SHA:

BASE_SHA=$(git rev-parse HEAD~1)  # 或 origin/main
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 | awk '{print $1}')
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

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 101 lines · 24 tokens per session scan A 4629ab5686d3

Subscribe to this mod's changes

requesting-code-review is a skill published in the GitHub repository jnMetaCode/superpowers-zh (7,965 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 844 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.