Individual skill
pr-explainer
A pull request explained for reviewers: what changed and why, a before and after, risks and the test plan, and a guided tour of the files, drawn from the branch commits and diff.
packages/content/local/skills/pr-explainer/SKILL.md
Source commit 400641fd6781fa0febad445984ee76440374736d
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,045
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- codex Repository topic
- cursor Repository topic
- dashboard Repository topic
- design Repository topic
- design-systems Repository topic
- design-tokens Repository topic
- figma Repository topic
- github-copilot Repository topic
- mcp Repository topic
- pull-request Declared skill tag
- pr Declared skill tag
- code-review Declared skill tag
- changes Declared skill tag
- diff Declared skill tag
- engineering Declared skill tag
- engineering Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,865 bytes
Read excerpt
# PR Explainer
**Intent.** Helps a reviewer understand a change in five minutes and review it in the right order. It is a guide to the diff, not a copy of it.
## Ground it
Write only what the sources say. Gather them yourself before writing a word:
- `git log --oneline <base>..HEAD` and `git diff --stat <base>...HEAD` (base: `main` unless the user says otherwise);
- `git diff <base>...HEAD -- <path>` for the files that matter, and the tests that changed;
- if `gh` is available and a PR exists, `gh pr view --json title,body,files,commits` and linked issues.
Keep the list of files, commits and refs you read: they go in a **Sources** section at the bottom of the page and in `sources` when you register (`register_open_design_artifact` with kind `html`). If something the document needs isn't in the sources, ask the user, or mark it plainly as an open question. Never invent numbers, dates, names or quotes.
