split-to-prs

Split uncommitted changes and branches into small reviewable pull requests.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill split-to-prs-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-to-prs
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/cursor/skills-cursor/split-to-prs
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill split-to-prs-ferrarifankid04

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large piles of mixed changes on a single branch are hard to review and risky to merge. This Skill analyzes your current work, proposes a reviewer-aligned split plan, and executes it as multiple small, focused pull requests. ## Core Features & Use Cases - Change Analysis: Compares committed and uncommitted work against the default branch and uses chat history to recover the intent behind each change. - Ownership-Aware Splitting: Reads CODEOWNERS and similar ownership files to align PR boundaries with natural reviewer responsibilities. - Safe Execution: Saves a recoverable snapshot via git stash refs before moving work, stages only named files or hunks, and never runs destructive git commands without approval. - Use Case: You have a week of mixed work on main touching three teams' code. The Skill proposes three independent PRs by ownership area, gets your approval, then creates branches, commits, pushes, and opens the PRs. ## Quick Start Ask the assistant to split the current branch's changes into small reviewable PRs and wait for the proposed split plan before approving.

Frequently Asked Questions about split-to-prs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large branch into multiple pull requests?

Compare the branch against the default branch to identify independent slices, then create a separate branch per slice, staging only the relevant files or hunks. This Skill proposes the split plan first and executes it only after your approval.

How to split uncommitted git changes into separate PRs?

Save a recoverable snapshot with git stash create and update-ref, then build each PR branch from the default branch by staging only the planned files. The working tree is never modified destructively during the process.

Does this Skill run destructive git commands?

No. It forbids reset --hard, clean -fdx, branch deletion, force-push, and history rewrites without explicit approval. It also creates a backup ref before moving work so all changes remain recoverable.

When should PRs be stacked instead of independent?

Stack PRs only when there is a real dependency between changes, ordering foundations before consumers. The default approach is independent PRs off the default branch, which keeps reviews parallel and diffs minimal.

How does the split decide PR boundaries?

It reads ownership signals like CODEOWNERS files to find natural reviewer boundaries, then splits independent owners or concerns while keeping tightly coupled changes together. A Mermaid diagram shows the plan when there are multiple slices.