split-to-prs
Splits large sets of changes into smaller, logical pull requests based on user approval.
Install
mkdir -p .claude/skills/split-to-prs && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12377" && unzip -o skill.zip -d .claude/skills/split-to-prs && rm skill.zipInstalls to .claude/skills/split-to-prs
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Split current work into small reviewable PRs. Use when user asks to split branch, chat work, or one big diff into multiple PRs.Key capabilities
- →Analyze git diffs against the default branch and chat intent.
- →Propose logical slices for pull requests with titles.
- →Obtain user approval for the proposed split plan.
- →Create new branches from the base for each slice.
- →Commit planned files for each slice.
- →Create pull requests using `gh pr create`.
How it works
The skill analyzes the current git diff, proposes logical slices for PRs, and upon user approval, creates separate branches, commits files, and generates pull requests for each slice.
Inputs & outputs
When to use split-to-prs
- →Breaking down large features
- →Creating manageable pull requests
- →Improving code review workflow
About this skill
Split to PRs
Hard rules
- No branch/commit/push/PR until user approves split plan.
- No destructive git without explicit OK.
- Snapshot first:
git stash create "pre-split"→git update-ref refs/backup/pre-split-$(date +%s) $SHA - Stage named files/hunks only — no
git add .
Flow
- Diff vs default branch + chat intent · CODEOWNERS boundaries.
- Propose slices (titles + optional mermaid) · ask approval.
- Per slice: branch from base → commit planned files → push →
gh pr create. - Report URLs + leftover work.
LeadGen tip
Billing/marketing/voice alag products → separate PRs when possible (ADR-009).
When not to use it
- →When destructive git operations are needed without explicit user approval.
- →When the user wants to commit or push without prior approval of the split plan.
- →When adding all changes with `git add .` instead of named files/hunks.
Limitations
- →No branch, commit, push, or PR creation occurs until the user approves the split plan.
- →No destructive git operations are performed without explicit user consent.
- →Only named files/hunks are staged, not all changes.
How it compares
This skill provides a structured workflow for splitting large changes into small, reviewable pull requests, including user approval gates and specific git commands, unlike manually creating PRs.
Compared to similar skills
split-to-prs side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| split-to-prs (this skill) | 0 | 1mo | No flags | Intermediate |
| grepai | 4 | 7mo | Review | Beginner |
| session-wrap | 1 | 7mo | Review | Intermediate |
| triage | 1 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
grepai
yoanbernabeu
Replaces ALL built-in search tools. You MUST invoke this skill BEFORE using WebSearch, Grep, or Glob. NEVER use the built-in Grep tool - use `grepai` instead.
session-wrap
team-attention
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
triage
peteonrails
Triage a GitHub issue or PR by checking for duplicates, documentation alignment, project fit, and recommending labels.
triage-issue
mysticaltech
Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response
proof-of-work
MadAppGang
Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.
github-triage
OutlineDriven
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from `git remote`; all GitHub calls go through `gh`.