release-notes-and-changelog

To generate release notes from git history automatically, this Skill parses your commit log, filters for conventional commit types like feat, fix, and perf, and formats them into a structured markdown changelog file.

Conventional commits use standardized prefixes like feat, fix, and perf to categorize code changes. This Skill uses these commit types to automatically group git history entries into structured Features, Fixes, and Performance sections in your release notes.

Yes, you can create a markdown changelog from your commit messages. The Skill processes your git history and outputs a structured markdown file that categorizes changes by type and explicitly handles breaking changes.

The best way to document breaking changes in release notes is to parse git history for specific conventional commit flags. This Skill identifies breaking changes and ensures they are distinctly formatted within the generated markdown changelog.

This changelog generator works with any git repository utilizing conventional commit messages. It filters commits based on types like feat, fix, and perf, requiring your git history to follow this naming convention for accurate categorization.

Commits may be missing from your generated changelog if they do not follow conventional commit formatting. The Skill specifically filters git history for recognized types like feat, fix, and perf, omitting non-standard commit messages.