review

Run a Claude Code review of the local git state through the companion script.

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 Claude's output verbatim to the user.

Locating the companion script:

• The companion script is scripts/claude-companion.mjs inside this plugin's root directory (the installed claude plugin directory that contains .codex-plugin/plugin.json).
• Always invoke it with an absolute path.

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 with --background so the companion detaches it.
• 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.
• Then ask the user exactly once, in plain conversation, with two options, putting the recommended option first and marking it "(Recommended)":
  • Wait for results
  • Run in background
• Do not ask any other questions.

Argument handling:

• Preserve the user's arguments exactly.
• Do not strip --wait or --background yourself.
• Optional trailing text after the flags is treated as review focus and passed through unchanged.

Foreground flow:

• Run:

node "<plugin-root>/scripts/claude-companion.mjs" review "$ARGUMENTS"

• Return the command stdout verbatim, exactly as-is.
• Do not paraphrase, summarize, or add commentary before or after it.
• Do not fix any issues mentioned in the review output.

Background flow:

• Run the same command with --background appended:

node "<plugin-root>/scripts/claude-companion.mjs" review "$ARGUMENTS" --background

• After launching, tell the user: "Claude review started in the background. Check @claude status for progress."

Sandbox requirements:

• The companion spawns the claude CLI, which needs network access to reach the Anthropic API.
• If the sandbox blocks the command or Claude reports a connection error, rerun the same shell command with escalated permissions and explain why in the justification.
• Do not work around a sandbox denial by improvising your own review or edits; the command's value is Claude's independent output.