release-notes

To generate human-readable changelogs from git commit history, this skill parses commit subjects and bodies, applying Conventional Commit standards to group changes into structured Keep-a-Changelog sections.

Yes, generating release notes with Conventional Commits automatically filters out internal noise like chore, test, and build commits to focus on user-facing changes rather than implementation details.

Breaking changes are detected when creating changelogs by parsing git commit subjects and bodies for specific breaking change indicators, highlighting them to warn users about migration requirements.

The best way to document version changes between the latest git tag and the current head is to parse that specific commit range and categorize the extracted changes into structured Added, Fixed, and Security sections.

Yes, Conventional Commit standards are required to generate Keep-a-Changelog sections, as the skill relies on these commit message conventions to accurately categorize changes and reduce internal noise.

A key limitation when parsing git commit bodies for release notes is that the skill requires strict adherence to Conventional Commit standards to correctly detect breaking changes and filter out internal noise.