review

Two modes. No argument, or the owner's own branch: branch mode. A PR number: PR mode.

Config: .claude/nauraiz-dev.json, with .claude/nauraiz-dev.local.json over it. Keys: branch.base (default main), branch.merge (default merge), models.review, gate.

Rules for both modes:

• "Stop" means: end your turn and wait.
• Never paste a diff into this thread. Write it to a file under git rev-parse --git-path and give the path to the reviewer; look at --stat only.
• These are review notes. Never write "Approved" or "LGTM", never submit an approving GitHub review.
• Never change the owner's checkout: no git checkout, git switch, gh pr checkout, git stash, no edits. Note git branch --show-current first; it must match at the end.
• Merge only when the owner says "merge" in this session.

Reviewer: the Agent tool with subagent_type nauraiz-dev:reviewer. Pass model only when models.review is sonnet, opus, haiku or fable; otherwise leave it out (the agent's own model). Dispatch only after the diff file is written. Its prompt: the diff file path, the base, the plan path and issue if any, and for a PR its title and body. It has no shell and works from the diff file; it returns findings by severity.

Branch mode

1. git fetch origin <base>. If git status --short lists changes, say they are not in the diff review, and that the gate result includes uncommitted changes.
2. Diff file: <diff> is what git rev-parse --git-path nauraiz-dev-review.diff prints. Run git diff origin/<base>...HEAD > "<diff>". Empty: say "Nothing to review against origin/<base>" and stop.
3. Dispatch the reviewer on <diff>. Meanwhile run node "${CLAUDE_PLUGIN_ROOT}/scripts/gate/run.mjs" once, from any folder in the project (it prints every exit code: never append echo $?, pipes or cd; re-run only after you changed code, or once with --plan <path> when a row says no plan for this branch). Exit 2: as the gate skill says.
4. Report: the findings ranked by severity, the gate output verbatim, what was not checked. End with what to fix before /nauraiz-dev:ship, or "No blocking findings". Do not fix anything unless the owner asks. Stop.

PR mode

1. gh pr view <n> --json number,title,body,author,baseRefName,headRefName,isCrossRepository,closingIssuesReferences.
2. <diff> from git rev-parse --git-path nauraiz-dev-pr-<n>.diff; run gh pr diff <n> > "<diff>". Dispatch the reviewer on it.
3. Gate on the PR head, in a temporary worktree outside the repo:
   • <tmp> is what node -e "console.log(require('os').tmpdir())" prints. <wt> is <tmp>/<repo>-review-<n>-<random> (<repo> this folder's name, <random> six hex characters you pick), never relative to the current folder. Quote it.
   • <wt> must not exist (git worktree list and the file system); if it does, stop.
   • git fetch origin pull/<n>/head, then git worktree add --detach "<wt>" FETCH_HEAD.
   • In <wt>, delete <wt>/.claude/nauraiz-dev.json and <wt>/.claude/nauraiz-dev.local.json, then copy this checkout's two files (those that exist) into <wt>/.claude/. The gate commands are then the owner's, but the PR still controls what they run (package.json scripts, tests, build files).
   • When isCrossRepository is true, before anything runs, warn: this runs the fork's code through the gate; ask, and stop until the owner answers.
   • If the gate needs dependencies, install them in <wt> (npm ci, flutter pub get).
   • node "${CLAUDE_PLUGIN_ROOT}/scripts/gate/run.mjs" --cwd "<wt>" (once; no echo $?, pipes or cd); add --plan "<wt>/<plan>" if the PR carries a plan for headRefName.
   • Then, only if git worktree add succeeded, git worktree remove --force "<wt>" with the exact <wt> this run created, never another path, even when a step failed.
4. If the /code-review skill is available, run it on PR <n> (no --comment).
5. Review notes: the reviewer's and /code-review's findings merged and ranked by severity, the gate output verbatim, what was not verified. Post them on the PR (gh pr comment) only if the owner asks. Stop.
6. Only after the owner says "merge": gh pr merge <n> --<branch.merge> (merge, squash or rebase), never --admin. After a merge only: close any of closingIssuesReferences still open (gh issue close), and offer the next kickoff prompt with the kickoff-prompt skill.