skills.rest
kkkaoru
kkkaoruCOMMUNITY
Explore all skills by this author →
𝕏@kkk4oruGitHub

split-to-prs

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

Updated Oct 15, 2019
Search Tags:#git#workflow#code review#pull requests#codeowners#branch splitting
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill split-to-prs-kkkaoru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: split-to-prs
Source: https://github.com/kkkaoru/dotfiles/tree/main/.cursor/skills-cursor/split-to-prs
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill split-to-prs-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large piles of mixed changes on a branch or in a dirty working tree are hard to review and risky to merge. This Skill turns one big set of changes into several small, focused PRs that reviewers can approve quickly, without losing any work. ## Core Features & Use Cases - Safe snapshotting: Creates a recoverable git ref backup before moving any work, so nothing is lost even when starting from dirty changes on the default branch. - Ownership-aware slicing: Reads CODEOWNERS and similar ownership files to propose PR boundaries that match natural reviewer responsibilities. - Approval-gated execution: Proposes a split plan (with Mermaid diagrams for multiple slices) and waits for explicit approval before creating branches, commits, or PRs. - Use Case: You finished a feature but your working tree mixes refactoring, tests, and docs. Ask to split the work, review the proposed PR plan, and get three clean PRs pushed with backup refs preserved. ## Quick Start Ask the assistant to split the current branch's changes into small reviewable PRs and propose a plan before creating anything.

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

How to split uncommitted changes into separate PRs safely?▼

Save a recoverable snapshot first using git stash create and update-ref to a backup ref, without modifying the working tree. Then stage only named files per slice, commit, push, and open each PR.

Does splitting PRs work with stacked dependent changes?▼

Yes, but stacking is used only when the dependency is real. The default is independent PRs off the default branch; when stacking is necessary, foundational changes are ordered before their consumers.

Can I split PRs without losing my uncommitted work?▼

Yes. A backup ref is created from a stash commit before any work is moved, and no destructive git commands like reset --hard or branch deletion are run without explicit approval.

When should I not split changes into multiple PRs?▼

Avoid splitting when changes are tightly coupled and cannot build or pass tests independently. Keep coupled changes together in one PR rather than creating broken intermediate states.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

sync-main

Fetch and merge the origin default branch into the current local branch.

Community
Basic
Zeyad-37Zeyad-37

ship-pr

Opens a pull request for a ready branch, then reviews and addresses feedback to merge.

Community
Intermediate
douglancedouglance
4

incremental-implementation

Splits multi-file code changes into independently tested and verifiable implementation slices.

Community
Intermediate
KrosebrookKrosebrook

Git Advanced Workflow Expert

Automates Git workflows for trunk-based development and monorepo management.

Community
Intermediate