change-log-generator

This Skill automates changelog generation by parsing Git commit history between version tags or the last entry to HEAD, classifying commits into structured categories like Breaking, Added, Changed, Fixed, and Security to ensure clear project evolution communication.

The best way to categorize Git commits is by processing commit message signals to classify changes into standard categories like Breaking, Added, Changed, Fixed, and Security, rewriting entries to clarify user impact and ensure structured documentation.

Yes, you can backfill missing changelog entries by processing historical Git logs between past version tags. This Skill classifies previous commits into structured categories and rewrites them to accurately document project evolution retroactively.

This changelog generator operates without external dependencies, processing your local Git history directly to produce a structured CHANGELOG.md. It relies solely on your existing commit messages and version tags to classify and format release documentation.

This Skill reads the Git commit history from the last version tag to HEAD, classifies the changes based on commit message signals, and generates a formatted CHANGELOG.md section detailing all user-facing modifications for release preparation.

You should automate changelog generation during release preparation or when backfilling historical documentation. Automating the parsing of Git history ensures all user-facing changes are consistently categorized and formatted according to best practices without manual effort.