메뉴
Use when completing tasks, implementing major features, or before merging to verify work meets requirements. 完成任务、实现主要功能或合并前验证工作是否满足要求时使用。 适用于：代码审查、code review、审查代码、检查代码质量、提交前审查。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when you have a written implementation plan to execute in a separate session with review checkpoints. 有书面实现计划需要批次执行并设置检查点时使用。 适用于：执行已有计划、按计划实现、批次执行任务、分批推进开发。
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup 实现完成、所有测试通过，需要决定如何集成工作时使用。 适用于：完成分支、合并分支、结束开发、提 PR、合并代码、完成功能开发。
Use when executing implementation plans with independent tasks in the current session. 在当前会话中执行含有独立任务的实现计划时使用。 适用于：执行计划、子代理开发、自动实现、开始实现计划、逐任务执行、两阶段代码审查。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. 遇到任何错误、测试失败或意外行为时使用，在提出修复方案之前。 适用于：调试、找 bug、修复问题、测试失败、排查错误、系统性调试、根本原因分析。
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions. 开始任何对话时使用 - 建立如何查找和使用技能的规则，在任何回应（包括澄清问题）之前必须调用技能工具。
Use when you have a spec or requirements for a multi-step task, before touching code. 当有规格或需求需要执行多步骤任务时使用，在编写任何代码之前。 适用于：写实现计划、制定开发计划、做规划、拆分任务步骤、编写执行方案。
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements. 完成任务、实现主要功能或合并前验证工作是否满足要求时使用。 适用于：代码审查、code review、审查代码、检查代码质量、提交前审查。 |
Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch code reviewer subagent:
Use Task tool with general-purpose type, fill template at code-reviewer.md
Placeholders:
{DESCRIPTION} - Brief summary of what you built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit3. Act on feedback:
[Just completed Task 2: Add verification function]
You: Let me request code review before proceeding.
BASE_SHA=$(git log --oneline | grep "Task 1" | head -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Dispatch code reviewer subagent]
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
PLAN_OR_REQUIREMENTS: Task 2 from docs/superpowers/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
[Subagent returns]:
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Ready to proceed
You: [Fix progress indicators]
[Continue to Task 3]
Subagent-Driven Development:
Executing Plans:
Ad-Hoc Development:
Never:
If reviewer wrong:
See template at: requesting-code-review/code-reviewer.md