Main entry point for code review. Auto-detects what to review and runs the multi-agent review engine.
From code-reviewnpx claudepluginhub misterraindrop/cc-skills --plugin code-review/reviewRuns Codex code review on local git state (working tree or vs base branch). Supports --wait/--background, --base <ref>, --scope auto|working-tree|branch.
/reviewReviews staged changes or recent commits across five axes—correctness, readability, architecture, security, performance—producing categorized findings with file:line references and fixes.
/reviewReviews HTML file for design anti-patterns, principles violations, and accessibility issues. Generates markdown report with status tables and recommendations.
/reviewPerforms multi-LLM code review on staged git changes, open PRs, or working tree, generating inline PR comments via orchestrate.sh orchestration.
/reviewReviews specified code scope via four specialists (quality, security, performance, architecture), producing summary, detailed findings, refactoring suggestions, prioritized action plan.
/reviewDispatches the reviewer agent to review current branch code changes against code quality principles.
Main entry point for code review. Auto-detects what to review and runs the multi-agent review engine.
/review [--depth quick|standard|deep] [--lang zh|en]
Options:
--depth: Review depth (default: auto-detected based on change size)
quick: Team Alpha only, 3 roles, 1 round, no challengestandard: Alpha + Beta, all roles, up to 3 rounds, challenge if neededdeep: Alpha + Beta, all roles, up to 5 rounds, always challenge, production checks--lang: Output language override (default: auto-detected from code comments)You are executing the /review command. Follow these steps precisely:
bash plugins/code-review/scripts/review-state.sh exists
If a state file exists:
bash plugins/code-review/scripts/review-state.sh read '.current_phase'current_phase is NOT "complete": ask user to resume or start freshcurrent_phase is "complete": ask user to view previous results or start freshIf starting fresh, delete old state:
bash plugins/code-review/scripts/review-state.sh delete
Detect what to review, in order of priority:
# 1. Check for staged changes
STAGED=$(git diff --cached --stat)
# 2. Check for unstaged changes
UNSTAGED=$(git diff --stat)
# 3. Fall back to last commit
LAST_COMMIT=$(git log -1 --oneline)
Tell the user what will be reviewed:
Detected: <N> staged files / <N> unstaged changes / last commit <hash> <subject>
Reviewing: <target description>
If --depth not specified:
# Count total changed lines
DIFF=$(bash plugins/code-review/scripts/collect-diff.sh staged 2>/dev/null || \
bash plugins/code-review/scripts/collect-diff.sh unstaged 2>/dev/null || \
bash plugins/code-review/scripts/collect-diff.sh commit HEAD 2>/dev/null)
LINE_COUNT=$(echo "$DIFF" | wc -l)
| Lines Changed | Default Depth |
|---|---|
| < 50 | quick |
| 50 - 500 | standard |
| > 500 | deep |
Show the user: Depth: <depth> (auto-detected, <N> lines changed)
DIFF_OUTPUT=$(bash plugins/code-review/scripts/collect-diff.sh <mode> [args...])
If diff collection fails, report the error and stop.
Follow the review-engine skill protocol exactly. The skill is defined at plugins/code-review/skills/review-engine/SKILL.md.
Execute all 6 phases:
Display the final report from the review engine.
If verdict is REQUEST_CHANGES:
Next steps:
1. Fix the issues listed above
2. Run /review again to verify fixes
If verdict is APPROVE:
Code looks good! Safe to commit/merge.
If verdict is NEEDS_DISCUSSION:
Some issues need further discussion. Review the findings above and decide on next steps.