explain-prlisted
Install: claude install-skill Skarlso/personal-workflow-skill
# Explain a Pull Request
Produce an architectural explainer for one PR: what it does, why it exists, how the
pieces fit, where the change lands, and a reading order that makes a 4,000-line diff
tractable.
This is an **explainer, not a code review**. Do not assess correctness line by line and
do not recommend merging or not merging. The one exception is the Questions section,
which surfaces design decisions worth a maintainer's attention — scope, trust
boundaries, dependencies, workflow constraints — never style or line-level nits.
## Step 1 — Fetch
```bash
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/explain-pr/scripts/fetch.py" <target>
```
`<target>` is `1234`, `owner/repo#1234`, or a PR URL. A bare number only works inside a
git repo. Prints the work directory — call it `$W` for the rest of this run.
## Step 2 — Read the outline
```bash
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/explain-pr/scripts/outline.py" $W
```
Read **only** this. It gives you the description, linked issues, commits, the file tree
grouped by churn, which files are tests / docs / generated, and the review discussion.
`$W/pr.diff` is often hundreds of KB and must never be read whole.
Pass `--per-dir 20` if a directory's "… N more files here" is hiding something you need.
## Step 3 — Read the code that matters
```bash
python3 "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}/skills/explain-pr/scripts/slice.py" $W <path-or-substring>... --context 2 --max-lines 250
```
`--context 2` drops