Changelog Generator

You can generate release notes from conventional commits by parsing git commit history and mapping the changes to Keep a Changelog sections like Added, Changed, and Fixed. This Skill automates that parsing to produce structured markdown or JSON outputs.

Yes, you can generate a changelog from a specific git range within CI pipelines. The Skill accepts git ranges or manual input to render structured release entries and optionally outputs machine-readable JSON for automated CI workflows.

Semantic version bumps are detected by parsing conventional commit messages in your git history. The Skill analyzes the commit types to determine whether a major, minor, or patch version bump is required for the release.

Yes, this changelog generator supports monorepo workflows and per-package updates. It can generate individual release entries for different packages within a monorepo and update the respective CHANGELOG.md files accordingly.

No external dependencies are required to parse git history into a Keep a Changelog format. The Skill operates independently using its internal scripts and references to map conventional commits into structured changelog sections.

The best way to update CHANGELOG.md is to consolidate your git history by parsing conventional commits. This Skill automatically renders the parsed changes into appropriate sections and applies optional date tagging to generate new release entries.