$ loading_
Trigger a code review against plans or requirements before moving forward.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Requesting Code Review" skill from askskill: 1. Download https://raw.githubusercontent.com/obra/clank/main/skills/collaboration/requesting-code-review/SKILL.md 2. Save it as ~/.claude/skills/requesting-code-review/SKILL.md 3. Reload skills and tell me it's ready
Act as a code review assistant. Check whether this implementation fully matches the following requirements, and identify logic flaws, missed edge cases, or unclear naming. Then provide concrete fixes.\nRequirements: Users can reset passwords, the reset link is valid for 24 hours, and all old tokens must be invalidated after reset.\nImplementation: <paste code>
A requirement-based review highlighting gaps, risks, and actionable fixes.
Review whether the implementation matches the development plan. Focus on module boundaries, completion of planned steps, and any unplanned complexity introduced. List issues by severity.\nDevelopment plan: <paste plan>\nImplementation: <paste code>
A review report comparing code to the plan, with deviations, severity levels, and next-step recommendations.
Before I proceed with the commit, quickly review this code for readability issues, potential bugs, missing tests, and security concerns. Return the results as a concise checklist.\nCode: <paste code>
A pre-commit checklist that helps fix key issues before continuing development.
Dispatch code-reviewer subagent to catch issues before they cascade.
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 code-reviewer type, fill template at code-reviewer.md
Placeholders:
{WHAT_WAS_IMPLEMENTED} - What you just built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit{DESCRIPTION} - Brief summary3. 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]
WHAT_WAS_IMPLEMENTED: Verification and repair functions for conversation index
PLAN_OR_REQUIREMENTS: Task 2 from docs/plans/deployment-plan.md
BASE_SHA: a7981ec
HEAD_SHA: 3df7661
DESCRIPTION: Added verifyIndex() and repairIndex() with 4 issue types
[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: skills/collaboration/requesting-code-review/code-reviewer.md
Write evergreen comments focused on what and why, not historical context.
Compare 2-3 approaches before execution to choose a stronger solution.
Plan with pseudocode first, refine approaches, then translate into working code.
Search past Claude Code chats to recover facts, decisions, and context.
Design systems by hiding implementation details behind domain-level interfaces.
Name code by domain meaning to improve clarity and team alignment.
Evaluate code review feedback rigorously before deciding whether to implement it.
Review code or branches for correctness, compatibility, architecture, tests, performance, and security.
Helps developers handle code review feedback with rigor, judgment, and effective responses.
Review code deeply across correctness, tests, security, performance, and product quality.
Review implementation plans for gaps, assumptions, and sequencing before coding starts
Run a structured code review before commit or release on local or PR branches.