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 owns the worktree, not the judgment. Settling which PR, checking it out, and tearing the checkout down again live here. 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, called at step 4 and again for every later round.

Nothing in this flow writes. No commits, no fixes, no pushes, no PR comments, no merge — even when the fix is one line and obvious. A review that edits its subject stops being a review. Findings go to the human, who decides what happens next. /squash-merge-and-clean-up merges; this skill only ever says whether it should.

A worktree because the review must not disturb anything. Other sessions share the primary checkout, and reviewing means checking out someone else's head, running their tests, and leaving build output behind. All of that happens in a directory this skill creates and — with permission — removes.

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: