What problem does it solve? Large, unfocused commits make git history unreadable, break git bisect, and turn code review into guesswork. This Skill automates the discipline of splitting staged and unstaged changes into small, semantically coherent commits with conventional commit messages. ## Core Features & Use Cases - Semantic change grouping: Analyzes git status and git diff output, then groups changes by meaning (a function plus its test, a bug fix across files) rather than by file. - Conventional commit messages: Derives type (feat, fix, docs, refactor, test, chore) and scope from the affected module, writing imperative-mood messages under 72 characters. - Safe staging and verification: Stages specific files or hunks (never git add -A), runs verification gates as separate commands before committing, and reports a summary of all created commits. - Use Case: After finishing a feature that touched eight files, ask the assistant to commit the work; it produces a sequence like feat(db): add B+ tree node split operation followed by its matching test commit, each independently compilable. ## Quick Start Ask the assistant to commit the current uncommitted changes as small conventional commits using the micro-commit workflow.
