split-branch

Split the current branch into multiple branches, each containing a single commit.

ALWAYS use the code:cli skill.

Context

• Current branch: !git branch --show-current
• All local branches: !git branch --list
• Remote tracking info: !git for-each-ref --format='%(refname:short) -> %(upstream:short)' refs/heads/

Arguments

The user passed in: $ARGUMENTS

If the user specified a base branch, use that. Otherwise, detect the base branch:

1. Check if there's an upstream tracking branch
2. Fall back to main or master (whichever exists)
3. If neither exists, ask the user to specify

Task

Step 1: Identify Commits to Split

Run: git log --oneline --reverse <base-branch>..HEAD

This shows all commits on the current branch that aren't on the base branch.

If there are 0 commits, inform the user there's nothing to split and stop. If there is 1 commit, inform the user there's only one commit so splitting isn't useful, and stop.

Step 2: Generate Semantic Branch Names

For each commit, generate a descriptive branch name based on the commit content:

1. Analyze the commit message subject line
2. Create a short kebab-case name (3-5 words max) that captures what the commit does
3. Use conventional prefixes when appropriate: add-, fix-, update-, remove-, refactor-
4. Avoid generic names - be specific about what changed

Examples of good semantic names:

• "Add user authentication model" → add-user-auth-model
• "Fix null pointer in checkout" → fix-checkout-null-pointer
• "Update API rate limiting" → update-api-rate-limits

Show the user a numbered list with the proposed branch names:

Splitting branch `<current-branch>` into <N> branches:

1. <short-sha> <commit-subject> → <semantic-branch-name>
2. <short-sha> <commit-subject> → <semantic-branch-name>
...

Ask for confirmation before proceeding. Use the AskUserQuestion tool with options:

• "Proceed with these names" (recommended)
• "Regenerate names" (generate alternative names)
• "Use numbered naming" (fall back to -1, -2, etc.)
• "Cancel"