branch-review-before-pr — Claude Code skill: gate a branch before a PR
branch-review-before-pr reviews a branch diff against the default base and reports merge-stopping defects before the PR exists. Edits nothing until you approve a fix.
no license 167 installs ★ 5 updated 2026-08-31
npx skills add ulpi-io/skills --skill branch-review-before-pr -a claude-codeWhat branch-review-before-pr does
The skill reads the whole branch diff against its base (usually origin/main or origin/master) and hunts for what tests skip: risky queries, race conditions, auth and trust-edge mistakes, side effects buried in conditions. It works in two rounds, and round one covers only issues that should stop the merge.
Each candidate gets checked against the code around it before it reaches the report, so problems already handled nearby fall away. Stopping issues come first, informational ones after, and a clean branch is stated as clean. Categories and suppressions live in checklist.md inside the skill.
No edit happens until you choose “Fix it now” for one particular issue. Every stopping issue gets its own question, so nothing is decided in bulk and nothing is fixed behind your back. The skill never commits, pushes or opens the PR. Formatting preferences stay out of the report — if you want style nits, this is not the tool.
What it helps with
- catch a risky query in the diff before it merges
- sort merge-stopping findings from informational ones
- check a branch for race conditions and auth holes
- decide on each blocker one at a time instead of in a batch
- confirm a branch is clean before opening the PR
Example prompts for the agent
- Run
branch-review-before-pron this branch againstorigin/main, focus on the data access layer. - Review the branch with
branch-review-before-pr; I only care about blocking findings. - Use
branch-review-before-prwith no focus hint and read the full diff againstorigin/master.
How to install branch-review-before-pr
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill branch-review-before-pr -a claude-code2Manually: put the files in place
~/.claude/skills/branch-review-before-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/branch-review-before-pr/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill branch-review-before-pr -a codex2Manually: put the files in place
.agents/skills/branch-review-before-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill branch-review-before-pr -a cursor2Manually: put the files in place
.cursor/skills/branch-review-before-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ulpi-io/skills branch-review-before-pr2Manually: put the files in place
.github/skills/branch-review-before-pr/SKILL.md1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill branch-review-before-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/ulpi-io/skills --path branch-review-before-prManually: put the files in place
.devin/skills/branch-review-before-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill branch-review-before-pr -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 branch-review-before-pr
How do I install branch-review-before-pr in Claude Code?
Run npx skills add ulpi-io/skills --skill branch-review-before-pr -a claude-code. The skill file lands at ~/.claude/skills/branch-review-before-pr/SKILL.md.
What does branch-review-before-pr do?
It reads the branch diff against its base and splits merge-stopping defects from the rest. Code changes only after you approve one specific fix.
How is it different from a bug hunt or a full-repo audit?
Its scope is the branch diff. A launch sweep across the repository belongs to go-live-audit, deep bug hunting to find-bugs, and styling is out of scope here.