What problem does it solve? Large, mixed-purpose commits make code review painful, hide the reason behind changes, and make it risky to revert a single fix. This Skill analyzes your working tree changes and splits them into multiple small, single-purpose commits that are independently reviewable and revertable. ## Core Features & Use Cases - Change Classification: Categorizes modified files into feature additions, bug fixes, refactoring, docs, tests, config, and dependency updates, then decides what to split versus group together. - Ordered Commit Creation: Stages files selectively (including git add -p for partial staging) and commits in a logical order: config, refactor, fix, feature, tests, docs. - Conventional Commits Messages: Every commit uses the Conventional Commits format in Japanese, with a mandatory self-review step before committing and test verification after each commit. - Use Case: You finished a work session with a Dockerfile, a new API endpoint, its tests, and README updates all uncommitted. The Skill splits these into four clean commits (chore, feat, test, docs) instead of one giant mixed commit. ## Quick Start Review my current uncommitted changes and split them into appropriately sized commits with Conventional Commits messages.
