review-pr-in-worktree
review-pr-in-worktree
human-only. Start this only when a human asks for it by name. If you arrived here from another skill, stop and get explicit confirmation before running any step.
Check a PR out into a worktree of its own and review it there: what it committed, whether its tests pass, whether it matches the plan it claims to implement, and where it has drifted from that plan. Report; do not repair.
This skill settles which PR; the rest is shared. Checking the PR out, reviewing it round by round, and tearing the checkout down again is the worktree review, which /review-pr-in-lane follows too. The review itself — what to read, how to run the gate, what to hold the code to, and the fixed report that ends in yes or no — is /review-a-pr-and-report, which that flow calls for every round.
Process
1. Establish the repo and the PR — use what you have, ask rather than search
Resolve both from what is already in front of you, in this order:
- The argument, if given (a PR number, a PR URL,
owner/name). - The current working directory's git remote and branch —
ghinfers the repo inside a clone, andgh pr statusnames the PR for the current branch. - Unambiguous existing context — this session opened the PR, or the human named one earlier and nothing since suggests otherwise.
If none of those settles it, or two of them disagree, ask, immediately — one question, as the first thing you do. Never pick a PR because it is the newest, because it is the only open one, or because its title looks like what the human was talking about. A review of the wrong PR wastes the whole session and reads as authoritative while it does it.