bobmatnyc/claude-mpm/requesting-code-review
Claude Code and agent skill by bobmatnyc/claude-mpm
- community
Checking that the SKILL.md file is still in the repository.
Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding
Install
npx vskill@latest install bobmatnyc/claude-mpm/requesting-code-reviewSKILL.md
Requesting Code Review
Dispatch code-reviewer subagent to catch issues before they cascade.
Core principle: Review early, review often.
Scope note: This skill is the review loop — how to dispatch thecode-reviewer subagent, gate on severity, and act on feedback. For thereviewer's checklist (what correctness/design/security/readability items toactually look for), see thecode-reviewskill.
When to Request Review
Mandatory:
- After each task in subagent-driven development
- After completing major feature
- Before merge to main
Optional but valuable:
- When stuck (fresh perspective)
- Before refactoring (baseline check)
- After fixing complex bug
Quick Start
1. Get git SHAs:
2. Dispatch code-reviewer subagent:
Use Task tool with code-reviewer type, fill template at Code Reviewer Template
Required 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:
| Severity | Action | |
|---|---|---|
| Critical | Fix immediately, don't proceed | |
| Important | Fix before next major task | |
| Minor | Note for later, can proceed |
See severity guidelines for details.
Integration with Workflows
Subagent-Driven Development:
- Review after EACH task
- Catch issues before they compound
- Fix before moving to next task
Executing Plans:
- Review after each batch (3 tasks)
- Get feedback, apply, continue
Ad-Hoc Development:
- Review before merge
- Review when stuck
Pushing Back on Reviews
If reviewer wrong:
- Push back with technical reasoning
- Show code/tests that prove it works
- Reference plan requirements
- Request clarification
Common Mistakes
Never:
- Skip review because "it's simple"
- Ignore Critical issues
- Proceed with unfixed Important issues
- Argue without technical justification
Always:
- Provide full context in review request
- Fix Critical issues immediately
- Document why you disagree (if you do)
- Re-review after fixing Critical issues
Examples
Need examples? See Review Examples & Workflows for:
- Complete review output examples
- Good vs bad review requests
- Review workflows for different scenarios
- How to act on different severity levels
- When and how to push back
Need template? See Code Reviewer Template for the complete subagent dispatch template.
Security
- Security scanPassed, 91 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingsrc/claude_mpm/skills/bundled/collaboration/requesting-code-review/SKILL.md
Popularity
- Repository stars
- 150
- Repository forks
- 34
- 7-day trend score
- 25
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/bobmatnyc/claude-mpm/requesting-code-review)