git-commit

To group git changes into atomic commits, this skill analyzes modified, staged, and untracked files to propose logical commit groupings and a safe staging order that preserves dependencies. It outputs a non-mutating commit plan file for review.

The best way to generate conventional commit messages from git diffs is to read repository changes and summarize the context for each file. This produces concise, scope-aware messages in imperative mood grouped by feature or fix.

You create a staging plan without altering git state by reading git status and diffs to suggest an ordered commit sequence. The skill outputs a plan file to your reports directory while strictly avoiding any actual git state changes.

Yes, you can use a commit plan to order commits by dependency rules for release prep. The analysis groups related edits and sequences them safely, ensuring foundational changes are committed before dependent feature updates.

Yes, the git-commit workflow supports analyzing both staged and untracked files. It discovers all repository changes, summarizes diffs and context for each modification, and groups them into coherent commits for features, fixes, docs, or configuration updates.