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.
npx skills add Leodorareluctant259/superpowers-zh --skill requesting-code-reviewgit clone --depth 1 https://github.com/Leodorareluctant259/superpowers-zhWrote 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.
[](https://agentmods.dev/skills/leodorareluctant259/superpowers-zh/requesting-code-review)<a href="https://agentmods.dev/skills/leodorareluctant259/superpowers-zh/requesting-code-review"><img src="https://agentmods.dev/badge/skills/leodorareluctant259/superpowers-zh/requesting-code-review.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00024 | $0.00823 |
| Opus 5 | $0.00012 | $0.00411 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
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 7d 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.
This is a copy
100% identical to requesting-code-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
请求代码审查
派遣 superpowers:code-reviewer 子代理来在问题扩散之前发现它们。审查者获得的是精心组织的评估上下文——绝不是你的会话历史。这样可以让审查者专注于工作成果而非你的思考过程，同时保留你自己的上下文以便继续工作。
核心原则： 早审查，勤审查。
何时请求审查
必须审查：
- 子代理驱动开发中每个任务完成后
- 完成重要功能后
- 合并到 main 之前
可选但有价值：
- 卡住时（换个视角）
- 重构之前（建立基线）
- 修复复杂 bug 之后
如何请求
1. 获取 git SHA：
BASE_SHA=$(git rev-parse HEAD~1) # 或 origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. 派遣 code-reviewer 子代理：
使用 Task 工具，指定 superpowers:code-reviewer 类型，填写 code-reviewer.md 中的模板
占位符说明：
{WHAT_WAS_IMPLEMENTED}- 你刚完成的内容{PLAN_OR_REQUIREMENTS}- 预期功能{BASE_SHA}- 起始提交{HEAD_SHA}- 结束提交{DESCRIPTION}- 简要说明
3. 处理反馈：
- Critical 问题立即修复
- Important 问题在继续之前修复
- Minor 问题记录下来稍后处理
- 如果审查者有误，用技术理由反驳
示例
[刚完成任务 2：添加验证功能]
你：让我在继续之前请求代码审查。
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[派遣 superpowers:code-reviewer 子代理]
WHAT_WAS_IMPLEMENTED: 会话索引的验证和修复功能
PLAN_OR_REQUIREMENTS: docs/superpowers/plans/deployment-plan.md 中的任务 2
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: 添加了 verifyIndex() 和 repairIndex()，支持 4 种问题类型
[子代理返回]:
优点：架构清晰，测试真实
问题：
Important：缺少进度指示器
Minor：报告间隔使用了魔法数字 (100)
评估：可以继续
你：[修复进度指示器]
[继续任务 3]
与工作流的集成
子代理驱动开发：
- 每个任务完成后审查
- 在问题叠加之前发现它们
- 修复后再进入下一个任务
执行计划：
- 每批（3 个任务）后审查
- 获取反馈，修复，继续
临时开发：
- 合并前审查
- 卡住时审查
红线
绝不要：
- 因为"很简单"就跳过审查
- 忽略 Critical 问题
- 带着未修复的 Important 问题继续推进
- 对合理的技术反馈进行争辩
如果审查者有误：
- 用技术理由反驳
- 展示证明其可行的代码/测试
- 要求澄清
参见模板：requesting-code-review/code-reviewer.md
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.
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.
- 7d ago First seen · 106 lines · 24 tokens per session scan A 81216a29c01e
requesting-code-review is a skill published in the GitHub repository Leodorareluctant259/superpowers-zh (5 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 823 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to requesting-code-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
simplify
This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code…
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
review-pr
This skill should be used when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR.
ainb-fleet:daemons
Runtime-health view of the four fleet daemons — phone bridge, notifyd, ATC, and the fleet auto-continue daemon — in one table. Each row reports state (running / stopped / unknown), pid, uptime, last activity, error count, and a HEALTH reason that distinguishes a clean stop from a crash (stale heartbeat) or a…
ainb-fleet:bridge
Native phone bridge — relay messages two-way between a chat channel (Telegram, Slack, and/or Discord) and your ainb sessions. Inbound chat messages route to a target session (by name: prefix, else a conductor- first default) and are delivered via tmux send-keys; the session's reply is captured from its JSONL…
resolve-fixed-pr-comments
Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.