use-review-request
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
When & Why to Use This Skill
This Claude skill automates the code review process by dispatching a specialized subagent to analyze changes, verify requirements, and identify potential issues before they are merged into the main codebase. It ensures high code quality and consistency across development tasks by providing automated, objective feedback based on git diffs and project requirements.
Use Cases
- Verifying major feature implementations against original requirements to ensure all criteria are met before merging.
- Catching technical issues, bugs, and architectural flaws early in the development cycle through automated subagent analysis.
- Providing a fresh perspective and baseline check for developers when they are stuck or planning significant code refactoring.
- Enforcing mandatory quality gates after completing sub-tasks to prevent the cascading of errors in complex projects.
| name | use-review-request |
|---|---|
| description | Use when completing tasks, implementing major features, or before merging to verify work meets requirements |
Dispatch autonome:code-reviewer subagent to catch issues before they cascade.
Core principle: Review early, review often.
When to Request Review
Mandatory:
- After each task in subagents-dispatch development
- After completing major feature
- Before merge to main
Optional but valuable:
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
How to Request
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 autonome: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 summary
3. Act on feedback:
- Fix Critical issues immediately
- Fix Important issues before proceeding
- Note Minor issues for later
- Push back if reviewer is wrong (with reasoning)
Red Flags
Never:
- Skip review because "it's simple"
- Ignore Critical issues
- Proceed with unfixed Important issues
- Argue with valid technical feedback
If reviewer wrong:
- Push back with technical reasoning
- Show code/tests that prove it works
- Request clarification