changelog

Generate a CHANGELOG by parsing your project's commit history using Conventional Commits format. This Skill reads commits, categorizes them (Added, Changed, Fixed, etc.), and outputs a Keep a Changelog compliant Markdown file with versioned entries and an Unreleased section.

Conventional Commits is a commit message format that structures metadata (type, scope, breaking changes); Keep a Changelog is the output format for release notes. This Skill uses Conventional Commits to parse and organize entries into Keep a Changelog's standardized categories and structure.

Yes. This Skill generates release note drafts from your commit history in Keep a Changelog format. Export the generated CHANGELOG or Unreleased section to GitHub Releases, reducing manual documentation work during version releases.

Semantic Versioning (SemVer) is recommended because this Skill organizes commits into version tags and Unreleased sections. While Conventional Commits alone suffice for categorization, SemVer ensures proper versioning structure in the final CHANGELOG output.

Commits without Conventional Commits format won't be categorized into Added, Changed, Fixed, etc. This Skill requires structured commit messages to map entries correctly; unstructured commits may be excluded or grouped generically in the CHANGELOG.

Conventional Commits with a breaking change indicator (exclamation mark or footer) are parsed and categorized as breaking changes. This Skill includes them in the appropriate CHANGELOG section, typically highlighted for visibility during major version updates.