review-pr

name	review-pr
description	Gather a PR or branch diff for review — decision tree for local working tree vs GitHub PR vs a fresh /tmp checkout, dumped to a file so nothing is lost to terminal truncation. Use when the user asks to review a PR, summarize a diff, or audit changes; hands off to `code-review` for the actual review and `stacked-diff-review` for the write-up.

Gather a Diff for Review

Three skills, one job. This skill gathers the diff. code-review is the review process — what to look for, how to verify a finding, when to auto-apply. stacked-diff-review is the output format. Load all three for a non-trivial PR.

---

1. Decide where the diff comes from

Prefer the local working tree whenever possible. A fresh checkout under /tmp is a last resort — only reach for it when the current directory genuinely cannot serve the review (wrong repo, or you need a clean tree and the user has unrelated uncommitted changes).

Decision order:

1. No PR reference, in a git repo — review the local branch. Detect an open PR via gh pr view --json number,url for context, but read the diff from the working tree: git diff <base>...HEAD (<base> = PR base or origin/HEAD), plus git diff and git diff --cached for any uncommitted changes. Mention uncommitted changes explicitly in the report.
2. PR reference provided, and we are inside the matching repo — verify by comparing gh repo view --json nameWithOwner to the PR's repo. If they match:
   • If the PR's head branch is currently checked out ( matches ), review the local tree as in (1).