Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
npx skills add https://github.com/J03Fr0st/s-kit --skill requesting-code-review复制此命令并粘贴到 Claude Code 中以安装该技能
Use before creative or behavior-changing work. Clarifies intent, explores options, writes a design file for approval, then stops before plan-feature.
Create a structured feature specification with design context and self-contained task files organized into parallel execution waves. Use this skill after brainstorming has produced an approved docs/design/YYYY-MM-DD-{feature-name}/design.md, or when the user provides an existing approved design.md and asks to turn it into actionable task waves. This skill produces local spec files under docs/specs/YYYY-MM-DD-{feature-name}/ using the same dated folder name as the design — no GitHub integration.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when a plan needs to be stress-tested against project language, CONTEXT.md, ADRs, existing code, or documented domain decisions before design approval or task planning.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
| name | requesting-code-review |
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
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:
build-feature task or waveOptional 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/specs/2026-05-27-deployment-plan/README.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]
Build Feature:
Ad-Hoc Development:
Never:
If reviewer wrong:
See template at: requesting-code-review/code-reviewer.md