一键导入
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Before any creative work — creating features, building components, adding capabilities, or modifying behavior — you must use this skill. Explore user intent, requirements, and design before implementation.
Use when executing implementation plans with independent tasks in the current session
Use when implementing any feature or bug fix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
调度 superpowers:code-reviewer 子代理,在问题扩散之前捕获问题。审查者获得精确定制的评估上下文 —— 不继承你的会话历史。这让审查者专注于工作成果,而非你的思维过程,并保留你自己的上下文用于持续工作。
核心原则: 早审查,常审查。
必须:
可选但有价值:
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. 处理反馈:
[刚完成任务 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 种问题类型
[子代理返回]:
优点:架构清晰,有真实测试
问题:
重要:缺少进度指示器
次要:报告间隔使用魔数 (100)
评估:可以继续
你:[修复进度指示器]
[继续任务 3]
Subagent-Driven Development:
Executing Plans:
临时开发:
绝不:
如果审查者错了:
参见模板:requesting-code-review/code-reviewer.md