release-notes

To generate a changelog from git history automatically, this Skill parses your commit messages to create entries following the Keep a Changelog format, categorizing changes based on their commit types.

Conventional commits parsing for release notes works by reading structured commit messages like feat:, fix:, and BREAKING CHANGE: to automatically categorize changes and determine the appropriate semantic version bump.

To determine the correct semantic version bump for a software release, this Skill analyzes parsed git commit types and suggests MAJOR, MINOR, or PATCH version increments based on the presence of breaking changes or new features.

Yes, you can automate changelog file updates and version manifest identification, as this Skill analyzes git logs to generate CHANGELOG.md content and locate your project's version manifest for automated version bumping.

Yes, you need to follow conventional commits to generate release notes accurately, because this Skill relies on parsing structured prefixes like feat: and fix: to categorize changes and determine semantic version bumps.

The best way to format release notes for software versioning is using the Keep a Changelog format, which this Skill generates automatically by parsing your git history and categorizing updates into standardized sections.