review

Those arguments must never reach a shell

$ARGUMENTS is substituted into this file as text, so a shell receiving it would evaluate whatever it contains — $(…), backticks, ;, |. Measured on the job commands: $(echo INJECTED) was executed before Node ever started.

Read the argument text, then assemble the command from fixed pieces only. Never place the argument text, or any fragment of it, into a command, and never pass it as a single quoted string. Every value below must be one you checked against its list and then wrote out yourself — chosen, never copied:

• --base <ref>: only if it matches ^[A-Za-z0-9._/~^-]+$
• --scope <value>: auto, working-tree, branch
• --engine <value>: auto, gemini, agy
• --model <value>: an alias (flash, pro, lite, …) or an id matching ^[A-Za-z0-9][A-Za-z0-9._-]*$
• --timeout <seconds>: only if it is entirely digits and between 30 and 3600
• --deep, --wait, --background, --json: literal flags, no value

If a value is not in its set, stop and say so rather than passing it through to find out.

Run a standard Gemini code review against the current git state through the shared plugin runtime. It is a pragmatic reviewer that finds real bugs, missing error handling, and incomplete code paths.

Raw slash-command arguments: $ARGUMENTS

Core constraint:

• This command is review-only.
• Do not fix issues, apply patches, or suggest that you are about to make changes.
• Your only job is to run the review and return Gemini's output verbatim to the user.

Execution mode rules:

• If the raw arguments include --wait, do not ask. Run the review in the foreground.
• If the raw arguments include --background, do not ask. Run the review in a Claude background task.
• Otherwise, estimate the review size before asking:
  • For working-tree review, start with git status --short --untracked-files=all.
  • For working-tree review, also inspect both git diff --shortstat --cached and git diff --shortstat.
  • For base-branch review, use git diff --shortstat <base>...HEAD.
  • Treat untracked files or directories as reviewable work even when git diff --shortstat is empty.
  • Only conclude there is nothing to review when the relevant working-tree status is empty or the explicit branch diff is empty.
  • Recommend waiting only when the review is clearly tiny, roughly 1-2 files total and no sign of a broader directory-sized change.
  • In every other case, including unclear size, recommend background.
  • When in doubt, run the review instead of declaring that there is nothing to review.
• Then use AskUserQuestion exactly once with two options, putting the recommended option first and suffixing its label with (Recommended):
  • Wait for results
  • Run in background

Argument handling:

• Preserve the user's arguments exactly.
• Do not strip --wait or --background yourself.
• Do not add extra review instructions or rewrite the user's intent.
• The companion script handles --background itself: it enqueues the review and spawns a detached review-worker, so the result outlives the foreground command. It does not outlive the session: SessionEnd removes this session's job records, finished ones included, so collect it with /gemini:result before the session ends. Do not use Claude's run_in_background: true for it.
• /gemini:review is native-review only. It does not take custom focus text.
• For an adversarial review that challenges design decisions, use /gemini:adversarial-review.
• --timeout <seconds> is not only how long the run may take: it is also a ceiling on how much output can be produced, because a turn that cannot finish emitting inside the window is killed. Raise it for a large scope or a batch; the AGY default is 120 seconds.
• --deep runs an agentic review: Gemini uses its read-only tools to inspect repo context beyond the diff (dependency manifests, untracked files, callers) before producing the same JSON findings. It is slower and uses more tokens; omit it for the fast, diff-scoped default. Pair --deep with --background for larger changes.