changelog-auto

To auto-generate a changelog from git commit history, the Skill analyzes conventional commit messages to categorize features, fixes, and breaking changes. It outputs a structured changelog file while optimizing token usage through git-native analysis and caching.

Conventional commit based changelog generation works by parsing standardized commit prefixes like feat and fix to identify change types. It automatically categorizes these changes and compiles them into a Keep a Changelog formatted document.

Yes, you can automatically detect the next semantic version from git commits. The Skill analyzes commit history for breaking changes, features, and fixes to determine whether to bump the major, minor, or patch version number.

The best way to integrate changelog generation into a release workflow is to run an automated script after merging code changes. This generates an updated changelog file and can be paired with committing and tagging for a complete release process.

Yes, you need conventional commit standards to automate your changelog effectively. The Skill relies on standardized commit messages to accurately categorize changes, detect the correct version bump, and generate a consistent formatted document.