commit-changes

To split unrelated git changes into separate conventional commits, the Skill analyzes git diff to identify logical changes, stages them in separate chunks, and applies the proper type, scope, and description for each commit.

Writing conventional commit messages for staged files involves enforcing a standardized format of type, optional scope, and description. The Skill automates this by planning logical staging and generating messages that adhere to the Conventional Commits specification.

To commit mixed updates without a messy git commit, the Skill breaks down multiple unrelated modifications into logical, modular units, creating separate, well-described commits for each change.

Yes, you can stage and commit code in chunks automatically. The Skill reviews the git diff to plan logical staging, then stages and commits the changes in modular chunks with appropriate conventional commit formatting.

You should use modular commits instead of a single large commit when you have made several unrelated changes, such as adding a feature, fixing a bug, and updating documentation, to maintain clear and consistent project history.

This conventional commits approach does not require specific git workflow tools. It operates directly on staged code changes using standard git diff analysis, requiring no additional dependencies to modularize and format commits.