requesting-code-review
Request and process code reviews with proper context. Use after completing significant implementation work.
When & Why to Use This Skill
This Claude skill automates and structures the code review process within the software development lifecycle. By providing templates for context gathering, reviewer dispatching, and feedback categorization, it ensures high-quality code standards, minimizes technical debt, and streamlines communication between developers and reviewers.
Use Cases
- Feature Completion Checkpoint: Generate comprehensive review requests after finishing major implementation work to identify logic flaws or architectural issues before merging.
- Subagent Task Validation: Integrate into multi-agent workflows to perform automated quality checks after each sub-task, preventing the compounding of errors.
- Standardized PR Documentation: Use the provided templates to create consistent pull request summaries, including change logs, testing results, and specific areas needing attention.
- Systematic Feedback Resolution: Categorize reviewer comments by severity (Critical, High, Medium, Low) to prioritize immediate fixes and document long-term technical debt.
- Refactoring and Bug Fix Verification: Ensure that complex refactors or critical bug fixes meet project requirements and maintain system stability through structured peer evaluation.
| name | requesting-code-review |
|---|---|
| description | Request and process code reviews with proper context. Use after completing significant implementation work. |
Requesting Code Reviews
Review early, review often - catch issues before they compound.
When Reviews Are Required
| Scenario | Timing |
|---|---|
| Each task in subagent-driven work | After each task |
| Major feature completion | Before integration |
| Before merging to main | Pre-merge |
| When stuck on a problem | As needed |
| Before refactoring | Pre-refactor |
| After complex bug fix | Post-fix |
How to Request Review
1. Gather Context
# Get commit range for review
git log --oneline -5
git diff main..HEAD --stat
2. Dispatch Reviewer
Task(code-reviewer, prompt="
Review the changes in commits [base]..[head]
**What was implemented:**
[Description of changes]
**Requirements reference:**
[Link or description of requirements]
**Areas of concern:**
[Any specific areas you want extra attention]
**Files changed:**
[List key files]
")
3. Process Feedback
| Severity | Action Required |
|---|---|
| Critical | Fix immediately - blocks all other work |
| High | Resolve before proceeding to next task |
| Medium | Address in current session if time permits |
| Low/Minor | Document for future improvement |
Review Request Template
## Code Review Request
**Commits:** [base-sha]..[head-sha]
**Branch:** [branch-name]
### Summary
[1-2 sentences on what changed]
### Changes by File
| File | Change Type | Description |
| ------------ | -------------- | -------------- |
| path/to/file | Added/Modified | [What changed] |
### Requirements
[Link to issue/spec or brief description]
### Testing Done
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
### Areas Needing Attention
- [Specific concern 1]
- [Specific concern 2]
### Questions for Reviewer
- [Any specific questions]
Handling Feedback
Agree with Feedback
- Acknowledge the issue
- Fix immediately (Critical/High) or document (Medium/Low)
- Respond with what was changed
Disagree with Feedback
- Never dismiss without explanation
- Provide technical justification with evidence
- Reference code patterns or documentation
- Explain trade-offs considered
- Be open to being wrong
Example Response
## Review Response
### Critical Issues
- **[File:Line]**: Fixed - [what was changed]
### High Priority
- **[File:Line]**: Fixed - [what was changed]
### Disagreement: [Issue]
I believe [current approach] is correct because:
1. [Technical reason]
2. [Evidence from codebase]
However, open to discussion if I'm missing something.
### Deferred
- **[Minor issue]**: Added to tech debt tracker for future
Integration Points
- After executing-plans batches
- After systematic-debugging fixes
- Before finishing branches (merge/PR)