PR Visualization — Review Report

Produce one deliverable: the PR review report, a self-contained tabbed HTML file at docs/pr-<number>.html. Three tabs come from bundled scripts (deterministic diff analysis); three you write after reading the diff (judgment). The report's job is to help a reviewer zero in on bad choices: undisclosed behavior changes, untouched callers, missing tests, asymmetries, weakened invariants.

Workflow

Let SKILL=/path/to/this/skill. Pick a scratch working dir for intermediate files (any temp location, e.g. WORK=<temp>/pr-review-<name>), with TABS=$WORK/tabs. Commands are POSIX-shell shaped; adapt to your shell.

1. Establish the diff

You need a local git repo containing both sides of the change:

• Branch/PR checked out locally: nothing to do. Scripts auto-detect the base (merge-base with, in order: origin/main, origin/master, main, master, origin/develop, develop). Pass --base <ref> when auto-detection is wrong, --head <ref> when the head isn't HEAD, or both for a commit range (--base HEAD~5). --worktree reviews uncommitted changes (untracked files included; on a mainline checkout the base falls back to HEAD itself; --head is rejected with it — the worktree IS the head).
• GitHub PR URL: clone the repo, then git fetch origin pull/<N>/head:pr-<N> && git checkout pr-<N>. If the user pasted the PR description, keep it — the Summary tab compares claims against the actual diff.
• Patch file only: git init a repo, commit the pre-images if available, apply the patch; if pre-images aren't available, note that blast radius and test-delta analysis will be partial.

2. Run the automated analyzers