commit-work

To write a Git commit message using Conventional Commits, you structure the message with a specific type, scope, and description. This Skill enforces the Conventional Commits standard and provides guidance on commit message structure and content.

To split large mixed changes into smaller logical Git commits, you stage each logical group of changes separately. This Skill guides you to break down mixed changes into smaller, reviewable units and helps you stage them interactively.

The best way to stage specific files for a Git commit is through interactive staging. This Skill helps you select exactly which changes belong in a commit by providing staging assistance for your version control workflow.

Commit splitting improves code review in version control by isolating unrelated changes into distinct, logical commits. This Skill reviews staged changes and splits work into logical units, creating high-quality, reviewable, and safe Git commits.

Yes, you can use this Skill for interactive staging and automatic message generation. It facilitates the creation of high-quality Git commits by reviewing staged changes and generating clear commit messages adhering to Conventional Commits.

You should not use automated commit message generation when your staged changes are large and mixed together. This Skill requires splitting work into logical units first to ensure the generated Conventional Commits message is accurate and safe.