split-to-prs
Skill0 starsChanged 2 months agoMITView on GitHub
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
11 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- paramcodes/skillsedited, first seen Nov 8, 2026
- ArangoGutierrez/claude-toolkitword for word, first seen Oct 15, 2026
- 0mlkrizzz655335v/claude-skills-zhtheir own version, first seen Oct 15, 2026
- leishifu666/skillsedited, first seen Oct 9, 2026
- Goodnessmbakara/codex-skillsword for word, first seen Oct 8, 2026
- p10ns11y/skillsedited, first seen Oct 3, 2026
Other versions11 projects use a version of this.
Word for word · 5
- ArangoGutierrez/claude-toolkit★ 4100% same
- Goodnessmbakara/codex-skills★ 1100% same
- Tsumugii24/skills★ 1100% same
- whyymj/page-agent-sdk★ 1100% same
- filipefalcaofs/repo-padrao★ 0100% same
Edited · 5
- p10ns11y/skills★ 292% same
- JameMy0001/antigravity-skills-hub★ 189% same
- leishifu666/skills★ 196% same
- theoklitosBam7/skills★ 198% same
- paramcodes/skills★ 099% same
Wrote their own version · 1
- 0mlkrizzz655335v/claude-skills-zh★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/base-rule.mdcCursor rule
- .cursor/rules/bash-style.mdcCursor rule
- .cursor/rules/groovy-implicit-return.mdcCursor rule
- .cursor/rules/groovy-style.mdcCursor rule
- .cursor/rules/markdown-style.mdcCursor rule
- .cursor/rules/python-style.mdcCursor rule
- automateSkill
- autopilotSkill
- canvasSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- create-subagentSkill
- cursor-blameSkill
- git-messageSkill
- goalSkill
- loopSkill
- migrate-to-skillsSkill
- new-repoSkill
- onboardSkill
- originSkill
- rename-chatSkill
- review-bugbotSkill
- review-securitySkill
- reviewSkill
- sdkSkill
- shareSkill
- shellSkill
- statuslineSkill
- update-cli-configSkill
- update-cursor-settingsSkill
The file
We split this skill into the rules it gives an agent
9 rules. 7 are common, 0 are distinctive, and 2 are very specific to this project.
7
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Common: line 13
Do not create branches, commit, push, or open PRs until the user approves the split plan.
- Very specific: line 14
Never discard user work. No destructive git commands (reset --hard, clean -fdx, branch deletion, force-push, history rewrite) without …
- Common: line 15
Always save a recoverable snapshot before moving work around.
- Very specific: line 22
Before proposing slices, find ownership signals for the touched paths (CODEOWNERS, nested ownership files, tools/ownership/PRODUCTOWNERS, …
- Common: line 26
Use judgment on detail. Usually PR titles are enough.
- Common: line 30
Default to independent PRs off the default branch.
- Common: line 32
Ask for approval before starting.
- Common: line 36
If there is uncommitted work, save a recoverable snapshot without changing the working tree:
- Common: line 49
Keep it short: PR titles and URLs, plus anything left on the starting branch or working tree.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Split to PRs
Turn one pile of work into a few small PRs.
Hard rules
- Do not create branches, commit, push, or open PRs until the user approves the split plan.
- Never discard user work. No destructive git commands (
reset --hard,clean -fdx, branch deletion, force-push, history rewrite) without explicit approval. - Always save a recoverable snapshot before moving work around. This often starts from dirty work on
main, so do not assume there is already a safe branch. - Stage only named files or hunks. No
git add ./git add -A.
1. Check the state
Compare the current work to the repo's default branch, including committed and uncommitted changes. Summarize the real slices you see, and use the chat history to recover intent.
Before proposing slices, find ownership signals for the touched paths (CODEOWNERS, nested ownership files, tools/ownership/PRODUCTOWNERS, or repo equivalents) and use them to identify natural reviewer boundaries.
2. Propose the split
Use judgment on detail. Usually PR titles are enough. Add a one-line scope note only when a title is unclear. Show a Mermaid diagram when there are multiple slices.
Optimize for reviewer-aligned PRs with minimal unrelated diff: split independent owners or concerns, keep tightly coupled changes together, and when stacking is necessary, order foundations before consumers.
Default to independent PRs off the default branch. Stack PRs only when the dependency is real.
Ask for approval before starting.
3. Execute the split
If there is uncommitted work, save a recoverable snapshot without changing the working tree:
SHA=$(git stash create "pre-split") if [ -n "$SHA" ]; then git update-ref "refs/backup/pre-split-$(date +%s)" "$SHA" fi- For each approved slice, create a branch from the right base, stage and commit only the planned files or hunks, then push and open the PR.
4. Report back
Keep it short: PR titles and URLs, plus anything left on the starting branch or working tree. Do not delete the backup ref or original branch unless the user asks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

