reviewcodelisted

# Code Review Review the diff for correctness bugs and cleanups: $ARGUMENTS ## Arguments - **Effort level**: the first token, when it abbreviates `low`, `medium`, `high`, `xhigh`, or `max`. Prefixes count, so `med`, `hi`, and `xh` all resolve. `--effort <level>` is an alias, valid anywhere in the arguments. Pass whichever you found to the Phase 1 script, which resolves it and prints a note if it cannot. Any other first token belongs to `<target>`, including a branch named `release` or a scope opening with `only`. - **`--fix`**: apply findings to the working tree after reporting. May appear anywhere. - **`--base <ref>`**: review against this base instead of the resolved default. - **`<target>`**: everything else, free-form. A PR number, branch, ref range, path, or a plain-English scope restriction ("only `src/parser.ts`", "focus on error handling", "skip the test churn"). - **`ultra`**: not supported here. Stop and tell the user to type `/code-review ultra` themselves. With no effort level, use the session's effort. Default to `medium`. ## Phase 0 — Scope Resolve the diff: 1. If `--base <ref>` was passed, the range is `<ref>...HEAD`. 2. Otherwise `git diff @{upstream}...HEAD`, falling back to `git diff main...HEAD`, then `git diff HEAD~1`. 3. If there are uncommitted changes, or the range diff is empty, also run `git diff HEAD` and include the working-tree changes. The review often runs before the commit. 4. `git diff` never shows untracked files, so a pre-commit review