PR Overview

Fetch a GitHub PR, review it through multiple specialized agents (read-only), collect any unresolved comments, and produce a self-contained HTML overview at pr-overview.html in the repo root so the user can read it in a browser.

This skill never modifies code, never commits, never pushes, and never resolves comment threads. It only produces an overview. For a workflow that also applies fixes, use pr-review-html; for one that addresses reviewer comments, use pr-review-fixer.

Phase 1: Fetch the PR

Resolve which PR to look at, in this order:

• An explicit number, URL, or branch name from the user
• Otherwise the PR for the current branch via gh pr view --json number

Pull what you need:

• gh pr view <pr> --json number,title,author,baseRefName,headRefName,body,url,state,commits,files,createdAt
• gh pr diff <pr> for the unified diff

Do not run gh pr checkout. This skill is read-only — the user may be on a different branch deliberately, and switching branches risks losing work. If the agents need code context beyond the diff, read files at the PR's headRefName via gh api rather than checking out.

Keep the PR body, author, createdAt, and url from the gh pr view JSON — these flow into Phase 6's pr_description section so the reader can see the author's framing verbatim.