| name | review |
| description | Review a PR for bugs, security issues, convention violations, and tenant isolation leaks. Pass a PR number (e.g. /review 101). Optionally add "fix" to auto-fix issues (e.g. /review 101 fix). |
PR Review Workflow
Review a pull request against project conventions and known pitfalls. Produces structured findings. Optionally dispatches a fix agent.
Arguments
- Required: PR number (e.g.,
/review 101)
- Optional:
fix — auto-fix critical/high issues after review (e.g., /review 101 fix)
Architecture
You are the orchestrator. You dispatch a review agent and present findings. If fix mode is requested and issues are found, you dispatch a fix agent.
Context rules:
- Read CLAUDE.md files yourself (they're small, ~12KB each) — you need them to validate findings
- NEVER read architecture/ARCHITECTURE.md or task files — not needed for code review
- The PR diff is the primary input — fetch it via
gh pr diff
Step 0 — Gather PR Metadata
gh pr view {PR_NUMBER} --json title,headRefName,baseRefName,changedFiles,additions,deletions,state
If the PR is closed/merged, inform the user and stop (unless they want to review anyway).
Determine scope from changed files:
- Files under
backend/ → backend scope
- Files under
frontend/ → frontend scope
- Both → both
Step 1 — Read Conventions
Based on scope, read the relevant CLAUDE.md files yourself:
- Backend →
backend/CLAUDE.md
