01
What this skill does
Use this skill when unrelated concerns, refactors, behavior changes, generated files, or separable hunks are mixed together. It plans logical batches, stages one batch at a time, and asks `git-commit` for the message. User authorization may cover an individual batch or the whole sequence; request confirmation for a prepared batch only when needed, and honor any requested per-batch confirmation.
02
When to use it
- 01Separating unrelated concerns in one working tree.
- 02Keeping refactors apart from behavior changes.
- 03Building local commits that are easier to review, revert, and explain.
03
How it works
- 01
Inspect current Git state, including staged and unstaged work.
- 02
Decide whether the changes need splitting and write a short commit plan.
- 03
Respect any existing index content before changing staged files.
- 04
Stage one logical batch at a time, including only the files and hunks that belong together.
- 05
Invoke `git-commit`, present the staged summary and message, then commit when covered by existing authorization or ask for that prepared batch's approval.
04
What you get back
- 01A proposed sequence of focused commits.
- 02One staged batch at a time with a matching Conventional Commit draft.
- 03Local commits within explicit user authorization for the batch or sequence.
05
Important boundaries
- 01Do not push as part of the split workflow.
- 02Do not collapse unrelated changes into one convenient commit.
- 03Do not overwrite existing user changes while reshaping the index.
06