skills.rest
tmalcolm-0607
tmalcolm-0607COMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-split

Split large feature branches into smaller draft pull requests via GitHub CLI.

Updated May 7, 2026
Search Tags:#git#workflow#github#code-review#branch-management#pull-request#pr-splitting
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pr-split-tmalcolm-0607
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-split
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/pr-split
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill pr-split-tmalcolm-0607

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Large, oversized pull requests are difficult to review, have significantly lower defect detection rates, and delay code merges, creating bottlenecks in software development workflows. This Skill automates the process of splitting large feature branches into smaller, focused PRs organized by separation of concerns to resolve these issues.

Core Features & Use Cases

  • Automated Diff Analysis: Categorizes changed files by domain (models, services, frontend, tests, etc.) and calculates line change metrics for each group.
  • Dependency-Aware Grouping: Organizes files into PRs respecting import order, test co-location, and merge dependencies to avoid broken builds.
  • Draft PR Generation: Creates cherry-picked branches and GitHub draft PRs with structured descriptions, merge order guidance, and review focus areas.
  • Use Case: For a 200-file feature branch, this Skill can split it into 10 focused PRs each under 20 files, reducing review time per PR from hours to 20-30 minutes and improving defect detection rates by 40% compared to large PRs.

Quick Start

Use the pr-split skill to split your current large feature branch into focused draft PRs targeting main, organized by code concern and dependency order.

Frequently Asked Questions about pr-split

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

FAQPage Schema
How do I split a large pull request into smaller, reviewable units?▼

To split a large pull request, this Skill analyzes your feature branch diff, groups changed files by domain and dependency order, then generates cherry-picked branches and focused draft PRs via GitHub CLI.

Why do large pull requests have lower defect detection rates?▼

Large pull requests cause low defect detection rates because reviewers face hundreds of files and thousands of changed lines, creating cognitive overload that causes missed defects and delayed code merges.

Can I automatically group changed files by domain for a git branch split?▼

Yes, you can automatically group changed files by domain such as models, services, frontend, and tests. The Skill categorizes files and calculates line change metrics for each group.

Does the PR splitting process preserve the original source branch for rollback?▼

Yes, the PR splitting process preserves the original source branch entirely. It generates new cherry-picked branches for the draft PRs, keeping the source branch safe for rollback.

What is the best way to organize split pull requests by separation of concerns?▼

The best way to organize split pull requests by separation of concerns is applying automated diff analysis that respects import order, test co-location, and merge dependencies to avoid broken builds.

How many files should a pull request have to maintain review efficiency?▼

To maintain review efficiency, a pull request should be kept under twenty files. This reduces review time to twenty to thirty minutes per PR and improves defect detection rates by forty percent.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
aberrantCodeaberrantCode
1

finishing-a-development-branch

Verify tests pass and merge, open a PR, retain, or delete a Git branch.

Community
Intermediate
adamdriscolladamdriscoll

git-cherry-pick

Apply a specific Git commit from a source branch to a target branch.

Community
Intermediate
mhaldermhalder
2

git-rebase

Perform interactive git rebases, squash commits, and resolve conflicts.

Community
Advanced