generate-changelog

Generate a changelog by extracting commits since the last Git tag, parsing conventional commit types (feat, fix, docs, refactor, test), and formatting them into categorized Markdown sections. This automates release notes compilation and ensures consistency across version documentation.

Conventional commits follow a structured format (type: description) that makes commit intent explicit. Changelog generation relies on this format to automatically categorize changes into Features, Fixes, Documentation, and other sections, reducing manual sorting.

Yes. This skill extracts commits between Git tags, groups them by type, and produces formatted release notes with version numbers and dates. Use it before each release to generate accurate, timestamped documentation automatically.

You need an initialized Git repository with commit history and at least one tag marking a previous release. The skill parses commits since the last tag, so existing version tags are required to determine the changelog scope.

The skill is optimized for conventional commits but can extract any commit message. Non-conventional commits may appear in a default section rather than categorized groups, reducing the clarity of your changelog output.

Changelog generation produces Markdown or plain text output with structured sections for each commit type, version numbers, release dates, and contributor links formatted for readability in release notes.