changelog-automation

Automatically generate a changelog from git history by determining the commit range since the last release, parsing commits with PR references, and categorizing them into structured sections. The Skill outputs formatted entries ready for your CHANGELOG.md file.

Yes, you can generate a Keep a Changelog formatted file from git commits. The Skill classifies your commit history into Added, Changed, Fixed, Security, and Breaking Changes sections, enriching them with PR numbers and author details.

Categorize git commits into changelog sections by parsing the commit range and applying classification rules. The Skill automatically sorts commits into Added, Changed, Fixed, Security, and Breaking Changes sections for release preparation.

Yes, this changelog automation works with multi-repo projects. The Skill applies automated changelog generation across multi-repo projects, determining commit ranges and parsing PR references to streamline documentation updates for complex releases.

Prepend a new release entry to an existing CHANGELOG.md by integrating the Skill with your release workflows. It generates the formatted entry from recent git history and automatically inserts it at the top of your current changelog file.

Yes, you can get version bump guidance when generating a changelog. The Skill analyzes your parsed git commits and categorized changes to provide version bump guidance alongside the structured changelog output.