pr-brieflisted

# PR brief Orchestrator — mixes `interrogate` + `blast-radius` (+ optional `why`) with a `gh` fetch to give the *reviewer* (you) a fast mental model of an incoming PR before any judgment pass. ## When to use - Teammate opens a PR and asks you to review - You are pinged on a PR in a repo / area you don't own - You need to write a good review comment but first need to understand *what* + *why* + *what breaks* ## When NOT to use - Your own WIP diff — use `quick-review` - Just judging quality — use `medium-review` or `advanced-review` (skip understanding step) - Understanding a random subsystem, not a PR — use `teach` (which chains `how` + `why` on any code) ## Inputs One of: - PR number: `<n>` (assumes `origin` remote) - PR URL: `https://github.com/<org>/<repo>/pull/<n>` - Local branch: `<branch>` (compare against `main` unless told otherwise) If none supplied, ask. ## Process ### 1. Fetch PR metadata + diff Use `gh` CLI: - `gh pr view <n-or-url> --json title,body,author,commits,files,baseRefName,headRefName,url` — metadata - `gh pr diff <n-or-url>` — full diff - `gh pr view <n-or-url> --json commits -q '.commits[].messageHeadline'` — commit list If gh fails or PR is local-only: - `git diff <base>...<branch>` - `git log <base>..<branch> --oneline` - Skip anything requiring API access, note gaps. Note down: files changed, LOC added/removed, linked issues (parse `#123`, `Closes #45`, `Fixes ABC-1234` from body + commits). ### 2. Invoke `interrogate` Delegate to `int