generate-changelog

To generate a changelog from git commits automatically, this Skill consolidates commit history and plan files into a standards-compliant changelog. It maps commit types to Keep a Changelog categories like Added, Fixed, Changed, and Security, then outputs a formatted block for release notes.

The best way to format release notes using Keep a Changelog standards is to consolidate codebase changes through automated grouping. This Skill maps inputs into Added, Fixed, Changed, and Security categories, applying de-duplication to ensure consistent project audits and version release documentation.

Yes, you can use plan files as a source for changelog generation alongside git history. The Skill consolidates changes from Git commits, plan-file metadata, or manual inputs, merging them into a single Keep a Changelog formatted block ready for your CHANGELOG.md.

De-duplication works by identifying overlapping entries across git commits, plan files, and manual inputs before grouping them. This ensures that the final Keep a Changelog output contains only unique items mapped correctly to Added, Fixed, Changed, or Security categories.

No external dependencies are required to automate changelog creation from commits. The Skill operates independently to map commit types to Keep a Changelog categories, deduplicate entries, and format the final output block for your release notes or project audits.

You should use manual inputs instead of git history when changes exist outside the codebase, such as documentation efforts or plan-based reporting. The Skill consolidates these manual entries alongside git data, applying the same Keep a Changelog formatting and de-duplication rules.