commit-message

You generate conventional commit messages for staged Git changes by running the workflow against your staged files. The skill analyzes the diff, enforces Conventional Commits patterns, and outputs a draft message to a .commit-message file at the repository root for your review.

The best way to ensure semantic Git commit messages is to use an automated generator that enforces Conventional Commits patterns. This skill validates your staged changes against the standard format and provides clear guidance to maintain strict semantic traceability.

To split unrelated staged changes into atomic commits, this skill checks the atomicity of your staged files and provides guidance. It detects unrelated changes and proposes splitting them into separate, focused commits to improve traceability and code review efficiency.

Yes, this commit message generator supports guidelines for Chinese-speaking developers. It provides clear bilingual instructions for both English and Chinese developers to ensure cross-language teams can maintain consistent Conventional Commits standards.

Yes, you can prevent accidental changes by using a strict commit execution protocol. This skill outputs a .commit-message file and follows a safe workflow that ensures only the reviewed message and staged changes are committed, preventing unintended modifications.