generating-changelog

Changelog generation analyzes your git commits to automatically produce structured release notes. The Skill processes commit history, categorizes changes by type, detects breaking changes, and formats output in Keep a Changelog, Conventional, or GitHub formats, ready to publish with version information and linked references.

Yes, the Skill handles monorepo-aware changelog generation with service scoping capabilities. It generates separate changelogs across service boundaries, ensuring each component's release notes remain accurate and isolated within larger repository structures.

Keep a Changelog uses organized sections by change type; Conventional Commits emphasizes semantic versioning with standardized commit messages; GitHub formats link directly to pull requests and issues. The Skill supports all three, letting you choose the format that fits your release workflow.

Semantic versioning automatically detects breaking changes and version bumps from commit analysis. The Skill applies version increments (major, minor, patch) based on commit types and breaking change indicators, embedding version numbers into generated release notes.

Yes, the Skill recognizes conventional commits (feat, fix, breaking change keywords) to categorize and structure changelog entries automatically. It parses commit messages to populate changelog sections, reducing manual effort during release preparation.

The Skill activates when editing changelog files or during release preparation, recognizing trigger keywords like 'changelog,' 'release notes,' and 'version.' It runs against a commit range to produce updated, publication-ready content with linked PR and issue references.