What problem does it solve? Commit histories written in freeform prose cannot be parsed by release-automation or changelog-generation tools, forcing maintainers to manually determine version bumps and draft release notes. This Skill provides the Conventional Commits v1.0.0 specification so every commit message follows a machine-readable grammar. ## Core Features & Use Cases - Message Grammar: Defines the type(scope): description structure with optional body and footers, including the ! marker and BREAKING CHANGE footer for breaking changes. - Type Vocabulary: Documents the spec-mandated types (fix, feat) and the widely-used conventional set (build, chore, ci, docs, perf, refactor, revert, style, test). - SemVer Mapping: Explains how fix maps to PATCH, feat to MINOR, and ! or BREAKING CHANGE to MAJOR, enabling automated version calculation from commit history. - Use Case: When preparing a release, review the commit history and write messages like feat(auth): add OAuth2 refresh-token support so tooling can compute the next version number and draft a changelog entry automatically. ## Quick Start Write a Conventional Commits message for my staged changes that adds a new export feature to the reporting module.