메뉴
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Perform a thorough self-review — or optionally request a review via browser_subagent — to catch issues before they cascade.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
git diff $BASE_SHA $HEAD_SHA
Read the template at code-reviewer.md in this directory and self-review against it.
Populate mentally:
{WHAT_WAS_IMPLEMENTED} — What you just built{PLAN_OR_REQUIREMENTS} — What it should do{BASE_SHA} and {HEAD_SHA} — Commit range{DESCRIPTION} — Summary of changes[Just completed Task 2: Add verification function]
BASE_SHA=$(git log --oneline | head -2 | tail -1 | awk '{print $1}')
HEAD_SHA=$(git rev-parse HEAD)
[Self-review using code-reviewer.md checklist]
Strengths: Clean architecture, real tests
Issues:
Important: Missing progress indicators
Minor: Magic number (100) for reporting interval
Assessment: Fix progress indicators before continuing
[Fix → Continue to Task 3]
Subagent-Driven Development:
Executing Plans:
Never:
See template at: requesting-code-review/code-reviewer.md
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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
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
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions