conventional-changelog

Generate CHANGELOGs from Conventional Commits with semver tagging.

320|3|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/mizchi/skills --skill conventional-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-changelog
Source: https://github.com/mizchi/skills/tree/main/tooling/conventional-changelog
Command: npx skills add https://github.com/mizchi/skills --skill conventional-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps release notes aligned with consistent commit formats by automating CHANGELOG generation and semver tagging across tooling ecosystems.

Core Features & Use Cases

  • Supports Conventional Commits formatting and maps to Keep a Changelog sections.
  • Compares and contrasts tooling options (release-please, changesets, git-cliff, towncrier, and conventional-changelog-cli) for cross-language release workflows.
  • Useful for teams standardizing release flows across npm, Rust, Python, Go projects, ensuring auditable release notes and predictable version bumps.

Quick Start

Generate a CHANGELOG automatically from your Conventional Commits using your preferred tool (release-please, git-cliff, or conventional-changelog-cli).

Frequently Asked Questions about conventional-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate CHANGELOG generation from Conventional Commits?

Automate CHANGELOG generation by mapping Conventional Commits to Keep a Changelog sections using tools like release-please, git-cliff, or conventional-changelog-cli, ensuring consistent release notes and predictable semver tagging.

How do Conventional Commits map to Keep a Changelog sections for release notes?

Conventional Commits map to Keep a Changelog sections by translating commit types like features and fixes into Added and Changed categories, encoding guidelines for breaking changes to ensure auditable release notes.

Can I use conventional-changelog tooling across npm, Rust, Python, and Go projects?

Yes, conventional-changelog tooling supports cross-language workflows across npm, Rust, Python, and Go projects by comparing tools like release-please, changesets, git-cliff, and towncrier for standardized release flows.

What is the best way to compare release-please, changesets, and git-cliff for cross-language workflows?

Compare these tools by evaluating their ecosystem support and mapping strategies: release-please and changesets for npm, git-cliff for Rust, and towncrier for Python, ensuring predictable version bumps across different languages.

How do I ensure predictable semver tagging when automating release notes?

Ensure predictable semver tagging by applying Conventional Commits guidelines that encode commit types and breaking changes, automatically mapping them to appropriate major, minor, or patch version bumps.

Do I need Conventional Commits formatting to use conventional-changelog-cli?

Yes, Conventional Commits formatting is required as it provides the structured commit messages that conventional-changelog-cli parses to automate consistent CHANGELOG generation and semver tagging.