code-review

# Code Review Run tiered review with strict output gates. ## Input Schema ```json { "scope": "optional working-tree|path|commit|pr; infer pr for bare number, #number, or PR URL", "target": "optional path, commit ref, PR number, PR URL, or current branch PR", "done_when": "blocking issues are identified with gate decision" } ``` ## Scope And Routing - `working-tree`: review unstaged/staged local changes. - `path`: review one file/directory diff. - `commit`: review a git diff revision spec, such as `COMMIT^!`, `BASE..HEAD`, or `BASE...HEAD`. - `pr`: review an open pull request: collect GitHub PR metadata/review evidence, fetch target branch, update local checkout with `gh pr checkout`, inspect local files; `target` may be PR number, URL, or current-branch PR. Input shorthand: - Canonical in-session: `$code-review 123` or `$code-review #123` => `scope=pr`, `target=123`. - Natural-language aliases: `code-review 123`, `code-review #123`, and `code-review PR 123` => `scope=pr`, `target=123`. - `code-review <github-pr-url>` => `scope=pr`, `target=<github-pr-url>`. - Bare number = GitHub PR number; do not ask for `scope=pr`. Never write to remote. PR scope may update local checkout to PR head; otherwise read-only except `.reports/codex/code-review/<timestamp>/` artifacts. Never pass `--force` to `git` or `gh`; if forced checkout seems needed to align local branch and PR head, stop, explain overwrite risk, and ask before retrying. To fix findings, switch to `code-remedia...