git-commit

Conventional commit messages standardize Git history and enable semantic versioning by enforcing a structure of type prefix, optional scope, subject, and body. This skill generates that structure automatically from your code change descriptions to reduce ambiguity and improve release notes.

Standard type prefixes enforced for conventional commit messages include feat, fix, docs, style, refactor, test, chore, perf, ci, and build. This skill automatically applies these prefixes to categorize your code changes accurately.

Yes, this tool supports adding optional scope, body, and footer to your commit messages. It provides templates and guidance to structure these sections according to the Conventional Commits specification for features, fixes, and refactors.

The best way to generate a commit message after a code refactor is to describe the refactoring changes you made. The tool then produces a conventional commit message using the refactor type prefix to standardize your messaging.

Yes, you can use this to generate conventional commit messages for code changes across any software project. It applies standard type prefixes and formatting to feature work, bug fixes, and refactors regardless of the specific platform.