| name | review |
| user-invocable | true |
| description | Runs quality review agents on demand — reviews code against VGV standards for architecture, tests, and simplicity, then writes one consolidated, numbered report. |
| when_to_use | Use when user says "review this code", "review my code", "code review", "review", "check this code", or "review before merging". |
| argument-hint | [path/to/files/or/directories (optional)] |
| allowed-tools | Bash(*/scripts/detect-review-scope.sh) Bash(gh *) Bash(glab *) |
| effort | high |
| compatibility | Designed for Claude Code (or similar products with agent support) |
Review code on demand
Run quality review agents. Review manually written code, assess existing codebases, or
check a branch before merging. Output is one consolidated report with stable,
numbered findings the user can act on by id.
Review Scope
<review_scope>$ARGUMENTS</review_scope>
Step 1 — Detect Scope
Parse the review scope above for optional file paths or directories.
If paths are provided:
- Validate each path exists (split on whitespace, check each token).
- Use provided paths as review scope. Derive the scope slug deterministically from the first
path: drop any file extension, then replace
/ with - (lib/auth/ → lib-auth,
lib/auth/token.dart → lib-auth-token). Same paths always give the same slug.
- Announce scope to the user and proceed to Step 2.
If no paths provided:
Run the scope detection script:
${CLAUDE_SKILL_DIR}/scripts/detect-review-scope.sh
- If
SCOPE=branch: use the listed files as scope. The scope slug is the current
branch name with / replaced by -. Announce scope summary (changed-file count, areas
affected) and proceed to Step 2.
- If
SCOPE=default: tell the user "You're on <CURRENT_BRANCH>. No branch diff
available." Use AskUserQuestion: "What would you like to review?" with options:
- Specify files or directories: accept paths; derive the slug from the first path as above.
- Review entire project: no scope constraint; slug
project.
Step 2 — Run Reviews
Run pwd and let <PWD> be the result — subagents may change directories, making relative
paths unreliable. Each run gets its own directory <PWD>/docs/code-review/<slug>/, so raw
per-agent reports go in <PWD>/docs/code-review/<slug>/raw/ (absolute) and one run never
clobbers another branch's kept report.
Run the default review agents below in parallel. Projects may add agents in their
CLAUDE.md (include them alongside the defaults) or replace the default set entirely.
