[BUG] `/ultrareview` misses untracked files — sends `git diff` only, no client-side warning

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

After an extensive coding session that produced both edits to tracked files and several new (untracked) files, I ran /ultrareview from the CLI. The command kicked off a remote web review that ran for several minutes.

It came back reporting that the code referenced files that "did not exist" — but those files did exist locally; they just hadn't been git add-ed yet. It appears /ultrareview only ships the output of git diff (or an equivalent that excludes untracked files), so roughly half of my new code was invisible to the reviewer.

Net result: a long, token-expensive review that surfaced a false-positive "bug" caused entirely by its own missing context, and that missed every real issue in the new files.

What Should Happen?

Either of the following would fix this; (a) is preferable:

(a) /ultrareview should include all uncommitted changes, including untracked-but-not-ignored files (effectively the behavior of bundling the working tree, or git add -N . && git diff). That matches what a human would expect "review my uncommitted work" to mean.

(b) At minimum, the client should detect that untracked files exist before dispatching the review, warn the user ("You have N untracked files that won't be included in this review"), and give them a chance to include them, skip them, or abort before spending tokens — ideally with a hint (e.g. git add -N .) for how to make the review useful.

Error Messages/Logs

Ultrareview findings

  bug_001 — False positive (but important to flag)

  Reviewer says src/agent/hooks/ is missing. It's present locally but untracked in git (git status shows it under "Untracked files"). The ultrareview ran against the committed/tracked state + diff, which didn't include these files. When you commit, must
  git add src/agent/hooks/ explicitly — a plain git add -u or staging only tracked changes would commit a broken tree. Same goes for tests/unit/agent/hooks/.

Steps to Reproduce

1. In any git repo, make edits to a tracked file.
2. Create one or more new files without running git add (so they are untracked but not ignored).
3. Run /ultrareview.
4. Observe: the review runs to completion, but its analysis is based only on the diff of tracked files. Any references from tracked files to the new untracked files are flagged as pointing to nonexistent files, and the untracked files themselves are not reviewed.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.112

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

Impact: a full review cycle was wasted. The "bug" the review surfaced was a false positive caused by its own missing context, and the actual new code (the part most likely to contain real bugs) wasn't reviewed at all.

Suggested minimum-viable client-side check before dispatch:

You have 7 untracked files that won't be sent to /ultrareview.
  [i]nclude them   [s]kip and continue   [a]bort