generate-changelog

Generate a changelog by parsing git commits using conventional commit conventions, which map commit types to categories like Added, Fixed, Changed, and Security. The Skill extracts commits between versions, groups them by category, removes duplicates, and formats output as a Keep a Changelog–compliant Markdown section.

Automate release notes by feeding git history, plan files, or manual entries into a changelog generator that enforces version, date, and source inputs. It consolidates changes by category and produces formatted Markdown sections ready for documentation.

Yes. The Skill supports plan-file sources alongside git commits and manual entries, integrating planned changes into release notes. It parses all source types, categorizes entries, and outputs Keep a Changelog–formatted Markdown sections.

Conventional commits are the primary input mechanism. The Skill maps commit types (feat, fix, chore, etc.) to changelog categories, groups related commits, deduplicates entries, and formats them into Keep a Changelog sections.

The Skill deduplicates changes within a changelog entry by consolidating identical modifications across commits and sources. Grouped by category, duplicates are merged into a single entry to keep release notes concise.

Provide version, release date, a source type (git, plan-file, or manual), and source data. The Skill validates these required inputs and handles error cases for empty or invalid data before generating output.