release-notes

To auto-generate release notes from git commits, the Skill detects your Git repository, derives changes from commits since the last release, and categorizes them into New Features, Improvements, Bug Fixes, and Documentation. It outputs a Markdown file with a date-stamped filename in the release-notes directory.

Yes, you can generate a changelog for a non-Git project. The Skill detects when a project is not a Git repository and instead builds the changelog from existing change documentation you provide, categorizing the changes and outputting a Markdown file.

The best way to format user-focused release notes is to categorize changes into New Features, Improvements, Bug Fixes, and Documentation. The Skill enforces this structured workflow and provides guidance on best practices for writing and formatting output for distribution.

Yes, release notes generation works without existing change documentation if your project is a Git repository. The Skill derives changes directly from commits since the last release, meaning you only need existing documentation if it is a non-Git project.

An auto-generated changelog includes sections for New Features, Improvements, Bug Fixes, and Documentation. It also supports optional technical notes to help teams and users understand what changed, why it matters, and how to use new features.