release-notes

You can generate release notes automatically by parsing Git commit history since the last tag, grouping the commits by type, and outputting a clean Markdown changelog. This automated changelog generation aggregates entries into structured sections for software releases.

Automated changelog generation works by parsing commit history since your last tag and grouping entries by type. It outputs a standard Markdown structure with sections for New Features, Bug Fixes, Performance, Breaking Changes, and Internal changes for your new version.

Yes, you can create a Markdown changelog suitable for GitHub releases. The output is flexible and formatted for CHANGELOG.md or GitHub releases, organizing commit history into categorized sections like New Features and Bug Fixes.

The best way to group commits by type for internal documentation is to automate the parsing of your commit history. This process categorizes entries into structured Markdown sections, providing clear internal release notes for stakeholders.

No specific dependencies are required to parse commit history into release notes. The Skill operates independently to read your Git commit history since the last tag and format it into a clean Markdown changelog.

When turning commits into release notes, the output includes standard Markdown sections for New Features, Bug Fixes, Performance, Breaking Changes, and Internal changes. This structure ensures your changelog clearly communicates software updates.