pr-retro — Claude Code skill: branch review and installation
The pr-retro skill measures a feature branch against its base and reports merge-readiness with recommendations. Run it before reviewing a PR.
no license 150 installs ★ 5 updated 2026-08-31
npx skills add ulpi-io/skills --skill pr-retro -a claude-codeWhat pr-retro does
pr-retro gathers Git data for the current branch against its base, including commits, file changes, and branch divergence. It derives branch metrics such as test-code ratio, focus, and change size, then scans the diff for secrets, .only markers, conflict markers, and debug code. The result is a GREEN, YELLOW, or RED verdict with recommendations for each signal.
In standard mode, the report also covers contributors, hotspot files, and hygiene findings, and writes a snapshot to .history/pr-retros/. With --quick, it skips the detailed report and snapshot. The workflow is read-only: it leaves code and Git state untouched, so fixes must be made separately. It stops on main, master, or develop, and requires commits relative to the base branch.
What it helps with
- judge whether a feature branch is ready to merge
- spot secrets and debug markers in a diff
- check test-code ratio and change size
- identify files where branch changes are concentrated
- get signal-based recommendations before a PR
Example prompts for the agent
- Run
/pr-retroto assess whether the current branch is ready for a PR. - Use
/pr-retro --quickfor a short branch check. - Compare the current branch with
devusing/pr-retro --base dev.
How to install pr-retro
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill pr-retro -a claude-code2Manually: put the files in place
~/.claude/skills/pr-retro/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-retro/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill pr-retro -a codex2Manually: put the files in place
.agents/skills/pr-retro/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill pr-retro -a cursor2Manually: put the files in place
.cursor/skills/pr-retro/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ulpi-io/skills pr-retro2Manually: put the files in place
.github/skills/pr-retro/SKILL.md1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill pr-retro -a gemini-cli2Platform CLI
gemini skills install https://github.com/ulpi-io/skills --path pr-retroManually: put the files in place
.devin/skills/pr-retro/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill pr-retro -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pr-retro
How do I install pr-retro in Claude Code?
Run npx skills add ulpi-io/skills --skill pr-retro -a claude-code. The skill file is placed at ~/.claude/skills/pr-retro/SKILL.md.
What does pr-retro do?
It derives branch metrics from Git data, scans the diff for pre-PR issues, and returns a merge-readiness verdict with recommendations. It does not modify code or Git state.
Can pr-retro review a branch with no commits against its base?
No. It stops when the current branch is main, master, or develop, or when there are no commits relative to the base branch.