make-changelog

To generate a changelog from git history, the skill parses your commit messages and formats them into a CHANGELOG.md file using the Keep-a-Changelog format. It intelligently identifies version ranges and categorizes commits into Added, Changed, or Fixed sections.

Yes, you can incrementally update an existing CHANGELOG.md file. The skill supports both fresh generation and incremental updates, identifying new version ranges and appending new commit categories without overwriting previous release notes.

Using conventional commits is recommended to categorize release notes properly. The skill categorizes commits into Added, Changed, and Fixed sections based on conventional commit types and observable impact, handling ambiguous scenarios through user interaction.

The best way to manage an Unreleased section in a changelog is to let the skill intelligently identify and process version ranges. It automatically groups recent untagged commits into an Unreleased section before promoting them to a tagged version.

Yes, this changelog generator works with ambiguous commit messages by orchestrating multiple subagents for efficient processing. It handles repository validation and interacts with you to resolve ambiguous scenarios when categorizing commits.

Your git commits might not show up in the generated changelog if they fall outside the identified version ranges or lack observable impact for categorization. The skill processes git history based on version tags and conventional commit formatting.