Split the most recent git commit into multiple logical commits without interactive rebase. Use when invoked as `$git-split` or when the user asks to split HEAD into smaller commits.
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Split HEAD into two or more logical commits by soft-resetting it into the working tree and recommitting groups.
Validate state:
git rev-parse --abbrev-ref HEAD
git status --porcelain=v1Stop if the working tree is dirty.
Identify target:
HEAD.HEAD.Inspect target:
git show --stat HEAD
git show --name-only HEADPropose logical groups before changing history. Ask for confirmation if grouping is ambiguous or if the commit appears already pushed.
Soft reset:
git reset HEAD~1
git status --porcelain=v1For each confirmed group:
git add <files>
git commit -m "<type>(<scope>): <description>"Follow repo commit conventions and keep each commit to one coherent concern.
Verify:
git log --oneline -6
git status --porcelain=v1Report the resulting commits. If the original commit was pushed, explain that a force-with-lease push is required.
Constraints: never use git rebase -i; never use git reset --hard.
phatblat/dotfiles
4d65cab
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.