commit-message

Conventional commit messages follow a strict format with a type (feat, fix, docs, style, refactor, perf, test, chore, ci, build), subject line limited to 50 characters in lowercase, and optional body wrapped at 72 characters. Stage your changes with git, then run the commit-message generator to analyze the diff and produce a formatted message ready to paste into git commit -m.

Conventional commits is a standardized format for git commit messages that enables automated changelog generation, semantic versioning, and clear commit history. It enforces consistent structure—type, subject, and body—making diffs easier to review and version control more traceable across teams.

Yes. This Skill analyzes staged changes and recent commit history to automatically generate conventional commit messages. It examines your git diff --staged output and produces a formatted message that complies with the strict type taxonomy and formatting rules, eliminating manual formatting.

Commit subjects must be present tense, no more than 50 characters, lowercase after the colon, with no period. Bodies should wrap at 72 characters and provide motivation and context. The conventional-commits specification enforces these constraints to keep history clean and machine-parseable.

The specification defines 10 types: feat (new feature), fix (bug fix), docs (documentation), style (formatting), refactor (code restructuring), perf (performance), test (testing), chore (maintenance), ci (CI/CD), and build (build system). Each type signals the nature of the change in your version control history.