changelog-cli

You can generate release notes from git history by analyzing commits between the last stable tag and HEAD, categorizing changes into New, Improved, Fixed, and Internal sections, and outputting a formatted markdown document ready for publishing.

The best way to automate release notes generation in a CI pipeline is to use a tool that computes the commit range from the last stable tag to HEAD, categorizes changes, and outputs formatted markdown release notes before publishing a stable release.

Parsing git tags helps compute ranges for release notes by identifying the last stable tag as a starting point, allowing the tool to analyze the subsequent git log up to HEAD and categorize changes accurately for the markdown output.

Yes, you can categorize git commits into New, Improved, Fixed, and Internal sections. This skill parses git history since the last stable tag, categorizes changes accordingly, and outputs a neatly formatted markdown document.

Yes, a previous stable tag is required to generate markdown release notes. The skill computes the commit range by parsing tags from the last stable release to HEAD to categorize changes and produce the formatted output.

Automated changelog generation prevents human error by parsing the exact git log range between the last stable tag and HEAD, ensuring all changes are categorized consistently into markdown sections for stable releases without manual summarization effort.