git-split

Split mixed-concern git branches into focused pull requests via cherry-pick.

2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/erclx/aitk --skill git-split-erclx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-split
Source: https://github.com/erclx/aitk/tree/main/claude/skills/git-split
Command: npx skills add https://github.com/erclx/aitk --skill git-split-erclx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the issue of mixed-concern branches that are difficult to review, prone to merge conflicts, and risky to deploy. It automates the process of separating unrelated commits into distinct, logical branches.

Core Features & Use Cases

  • Automated Branch Splitting: Uses cherry-pick to move commits from a cluttered branch into new, focused branches based on their specific concern.
  • Intelligent Grouping: Automatically classifies commits into independent or stacked workflows, ensuring the correct base branch is used for each.
  • Safety Guards: Includes built-in checks for dirty working trees, banned characters in commit messages, and branch naming conventions to ensure high-quality pull requests.

Quick Start

Ask the AI to split the current branch into focused pull requests based on the commit history.

Frequently Asked Questions about git-split

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

FAQPage Schema
How do I split a git branch with mixed commits into separate pull requests?

You can separate unrelated commits by using automated cherry-pick operations to move them from a cluttered branch into new, focused branches. The skill intelligently groups commits into independent or stacked workflows, ensuring the correct base branch is used for each partition.

What's the best way to handle a messy git branch before code review?

The best way to handle a messy branch is to partition it into focused, reviewable pull requests. This approach automatically classifies commits by concern, separating unrelated features or fixes to reduce merge conflicts and deployment risks.

Does automated branch splitting check for a dirty working tree?

Yes, automated branch splitting includes safety guards that check for a dirty working tree before partitioning. It also enforces branch naming conventions and validates commit messages for banned characters to ensure high-quality pull requests.

Can I separate stacked git commits into sequential merges?

Yes, you can separate stacked git commits into sequential merges. The skill intelligently classifies commits into stacked workflows, ensuring the correct base branch is used for each new pull request to maintain sequential merge safety.

How do I enforce branch naming conventions when creating new pull requests?

You can enforce branch naming conventions during automated branch splitting. The skill includes built-in safety guards that validate new branch names and check for banned characters in commit messages to ensure pull request template adherence.