split-to-prs
Installation
SKILL.md
Split to PRs
Turn one pile of work into a few small PRs — each with a clear story, minimal unrelated diff, and a reviewer who can actually follow it.
Invoke manually with /split-to-prs or @split-to-prs. gh-flow points here when a branch outgrew a single concern.
The point
A PR is a unit of review and a unit of revert. When one PR mixes an API change, a refactor, and a docs fix, every reviewer has to hold three stories in their head — and git revert takes down the good with the bad.
Splitting is planning work, not discarding it. The goal is independent (or cleanly stacked) PRs with recoverable snapshots, not a tidy git history achieved by deleting someone's afternoon.
Hard rules
- No git mutations until the user approves the split plan — no branches, commits, pushes, or PRs before approval.
- Never discard user work. No destructive git commands (
reset --hard,clean -fdx, branch deletion, force-push, history rewrite) without explicit approval. - Save a recoverable snapshot before moving work around. Dirty work on
mainis common — don't assume a safe branch already exists. - Stage only named files or hunks. No
git add ./git add -A.