Review PR — take a pull request the last mile

Act as the senior engineer who ships the PR, not just reads it. Anchor every claim to live git/GitHub state, targeted tests run on the PR head, and — when UI changed — a real browser smoke with real screenshots.

This skill does not replace line-by-line diff review. When the user wants a code review of the changes themselves, run the agent's built-in review tooling (e.g. /code-review) and merge its findings into the readiness verdict below. What this skill owns is the release path: live state, verification, smoke evidence, merge readiness, and what happens after merge.

Core Workflow

1. Confirm the workspace state first.

   • Run git status --short --branch.
   • Do not mix local edits into the PR verification. Preserve user work with a named stash or separate worktree only when appropriate.
   • Identify the PR base branch from gh pr view; do not assume it is main.
   • Fetch the current base branch and PR head before anything else.

2. Read live PR truth.

   • Use gh pr view <number> --json number,title,body,headRefName,baseRefName,isDraft,mergeStateStatus,reviewDecision,statusCheckRollup,files,commits,url.
   • Use gh pr diff <number> or git diff origin/<base-branch>...refs/remotes/pr/<number>.
   • If a PR disappeared from the open list, check whether it merged or closed.