git-conventional-commits

To split working tree changes into conventional commits, this Skill organizes uncategorized changes and proposes one semantic commit at a time, pausing for explicit user approval before applying each commit to your Git workflow.

The approval loop for Git commit management requires explicit user confirmation before each commit is applied. The Skill proposes a single conventional commit and pauses, ensuring you maintain strict control over the staging and commit sequence.

The enforced conventional commit types for staging changes are feat, fix, test, chore, refactor, style, and docs. The Skill implements this strict format to ensure semantic, readable commit messages and accurate changelogs.

To ensure Git changelog accuracy during code review, the Skill enforces strict conventional commit formats and an approval loop, guarding against unreviewed changes by requiring topic-based staging and user confirmation before applying each commit.

Yes, you can use conventional commits to organize uncategorized Git changes. The Skill takes a set of mixed working tree modifications and sequences them into structured commits, prompting for your confirmation prior to each application.