git-commit-conventional

To generate conventional commit messages, the Skill analyzes your staged git diffs to determine the appropriate type, scope, and subject. It ensures strict formatting compliance by enforcing imperative mood and length constraints for your project history.

The conventional commits specification structures code history by enforcing a strict format with type, scope, and subject. This Skill applies types like feat, fix, docs, and refactor to standardize version control logs and clarify project changes.

Yes, you can automatically determine the scope and type for your git commit. The Skill dynamically analyzes your staged changes to assign appropriate types such as build, ci, chore, perf, or test, along with a dynamically determined scope.

The generated commit subject strictly follows imperative mood and length constraints. By analyzing staged diffs, the Skill enforces these grammatical and structural rules to ensure your version control messages meet conventional commits standards.

The best way to automate commit message formatting is to use this Skill on your staged changes. It automatically differentiates between features and bug fixes by applying the correct feat or fix type, ensuring clear and consistent code history.

You should use specific conventional commit types like chore, ci, or docs when your staged changes match their respective purposes. The Skill analyzes your diffs to assign these types dynamically, ensuring accurate categorization for non-feature updates.