parallel-review
Parallel Code Review
Runs multiple code review tools simultaneously for comprehensive feedback.
Workflow
Step 1: Determine Scope
Figure out what to review:
- If user specifies files → review those files
- Otherwise → review all unstaged/staged changes via
git diff
Step 2: Launch Parallel Reviews
Run ALL of the following in parallel using the Agent tool:
-
Code Review Agent (
subagent_type: "pr-review-toolkit:code-reviewer")- Prompt: "Review the following changed files for bugs, logic errors, code quality, and adherence to project CLAUDE.md conventions: [list files or describe changes]"
-
CodeRabbit Review Agent (
subagent_type: "coderabbit:code-reviewer")- Prompt: "Review the code changes for bugs, security issues, and quality problems: [list files or describe changes]"
-
Silent Failure Hunter (
subagent_type: "pr-review-toolkit:silent-failure-hunter")- Only include this if the changes involve error handling, try-catch, or fallback logic
- Prompt: "Check for silent failures and inadequate error handling in: [list files]"
Step 3: Synthesize Results
After all agents complete:
- Combine findings, deduplicating overlapping issues
- Prioritize: Critical > Serious > Moderate > Minor
- Present a unified summary with actionable fixes
- If issues are found, offer to fix them
Step 4: Fix (Optional)
If user agrees to fixes:
- Apply fixes for critical and serious issues
- Re-run
/fix-ts-errorson changed files - Briefly confirm what was fixed
For UI Changes
If the changes include frontend/UI code, also run in parallel:
/web-interface-guidelinesreview/ui-skillsreview/ramsaccessibility review
Quick Mode
If user says "quick review" — run only the code-reviewer agent (skip coderabbit and silent-failure-hunter).
More from bhagyamudgal/skills
review-pr
Deep, anti-slop review of a GitHub PR. Grounds findings in the linked issue's intent, runs Claude + CodeRabbit reviewers in parallel, then critic-passes the findings before printing. Use when user says "review this pr", pastes a GitHub PR URL, or asks "check this pull request". NOT for local uncommitted changes — use /parallel-review for those.
11fix-pr-review
Triage and fix CodeRabbit / review-pr findings on a GitHub PR, then reply + resolve conversations. Classifies each finding (FIX/DISMISS/DEFER/DISAGREE/NEEDS-INPUT), runs /done, posts specific replies. Use on CodeRabbit review URLs, PR URLs, or local review files. Pairs with /review-pr.
7forge-plan
Use when starting any non-trivial feature or design task that needs the full idea-to-implementation pipeline. Also use when user says "forge", "forge plan", "full pipeline", or wants the complete AI development workflow before shipping.
6harden-plan
Pre-code quality gate that runs /review-pr's anti-slop lens against a written plan BEFORE any code is written. Grounds the plan against the real codebase, runs 11 category checks (security, concurrency, round-trip, control-flow, error-handling, pattern-consistency, plus /review-pr's Q1-Q6), then grills the user one question at a time until the plan is hardened. Use when the user says "harden my plan", "check my plan", "grill my plan before I code", "lint this plan", or invokes `/harden-plan` explicitly. Also invoke proactively after `/superpowers:brainstorm` or `/grill-me` completes with a written plan and before any implementation begins. Do NOT invoke after coding has started — redirect to `/review-pr` / `/fix-pr-review` in that case.
6project-discovery
Deep project discovery and architecture planning. Use when starting a new project, when user says "new project", "let's build", or asks for help architecting/planning a non-trivial application.
5qa
Use when user says "qa", "test the flow", "QA this", "verify the UI", "test this page", "check if it works", "end-to-end check", or after completing code changes that affect UI and need manual verification replaced by automation.
4