← ClaudeAtlas

claude-code-reviewlisted

Deep code review via Claude subagent — reviews uncommitted changes by default, loops until no critical issues remain. Use after /qq:test passes, before /qq:commit-push.
tykisgod/quick-question · ★ 11 · Code & Development · score 71
Install: claude install-skill tykisgod/quick-question
> **Invoke scripts via `${CLAUDE_PLUGIN_ROOT}/bin/<name>`.** That env var is set by Claude Code for every plugin context and gives the absolute path to the marketplace clone — no PATH or cwd assumptions. Bare-command invocation (e.g. `claude-review.sh`) is NOT reliable: the plugin never puts its scripts on PATH, so bare calls exit 127. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Arguments: $ARGUMENTS - No arguments: review uncommitted changes (default) - `--base <branch>`: full branch diff against a base - `--commits`: review only the most recent commit - `--files "a.cs b.cs"`: explicit file list ## Review Scope Selection (no arguments) **Default: uncommitted changes.** Run `git diff --name-only HEAD -- '*.cs'` to get the list of changed files. This is the most common case — code has been written but not yet committed. Override order: 1. **User specified a scope** (e.g. "review Phase 8") → follow user intent 2. **No uncommitted changes but branch has commits** → `git diff --name-only develop...HEAD -- '*.cs'` 3. **User says "review the whole branch"** → `--base develop` Pass the file list to the review script as `--files`. ## Execution Flow ### 2–5. Automated Review Loop **Loop automatically — do not ask the user between rounds.** Stop when any of the following is true: - No `[Critical]` issues in the review result - 5 rounds have been completed - Two consecutive rounds with no new c