Hyper PR Review

Treat each finding as a hypothesis with a concrete trigger and a disproof attempt. Review enough of the affected behavior to catch important omissions, then report only supported issues. Precision and coverage both matter; a quiet report over unread code is not a successful review.

Use cross-model-review for independent reviewer dispatch and super-good-pr for PR descriptions. These skills compose when needed, not as a mandatory pipeline. Preserve the user's scope and authorization; a request to review and fix authorizes both roles in sequence.

Establish Scope and Intent

For a PR, capture the live base and head, changed files, and check results:

gh pr view <n> --json number,title,body,baseRefName,baseRefOid,headRefName,headRefOid,isDraft,url
gh pr diff <n> --name-only
gh pr diff <n>
gh pr checks <n>

Re-read both base and head after capture. If either changed, recapture the affected scope. A local review uses the requested base and explicit commits; use the parent branch for a stack. Fetch when remote freshness matters, without assuming every repo has an origin/main.