split-to-prs

Split uncommitted or committed changes into small reviewer-aligned pull requests.

Updated May 28, 2023
One-click install
npx skills add https://github.com/steveulrich/ProjectB --skill split-to-prs-steveulrich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: split-to-prs
Source: https://github.com/steveulrich/ProjectB/tree/main/.cursor/skills/split-to-prs
Command: npx skills add https://github.com/steveulrich/ProjectB --skill split-to-prs-steveulrich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large piles of changes on a single branch are hard to review and risky to merge. This Skill analyzes your current work against the default branch and proposes a plan to split it into small, independent, reviewable PRs before touching any git state. ## Core Features & Use Cases - State Analysis: Compares committed and uncommitted work against the repo's default branch and summarizes the real slices of change. - Ownership-Aware Splitting: Reads CODEOWNERS and other ownership files to align PR boundaries with natural reviewer groups. - 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 changes on main spanning three teams. Ask to split the work, approve the proposed plan, and get three independent PRs each routed to the right reviewers. ## Quick Start Ask the assistant to split the current changes on this branch into small reviewable PRs and propose a split plan first.

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, group changes by owner or concern, then create a branch per slice and commit only the planned files. This Skill proposes the split plan first and executes only after your approval.

How to split uncommitted changes into separate PRs in git?▼

Save a recoverable snapshot with git stash create and update-ref, then stage only named files or hunks per slice onto new branches. Never use git add . or git add -A, which would mix unrelated changes together.

Does this Skill run destructive git commands?▼

No. It explicitly forbids reset --hard, clean -fdx, branch deletion, force-push, and history rewrites without explicit approval. It always saves a backup ref before moving work so nothing is lost.

When should PRs be stacked instead of independent?▼

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

How does the split decide reviewer boundaries?▼

It reads ownership signals such as CODEOWNERS, nested ownership files, or tools/ownership/PRODUCTOWNERS for the touched paths. Slices are aligned to those owners so each PR reaches a natural reviewer group.