changelog-generator

Generate CHANGELOG entries from commits using conventional commits and semantic versioning.

25|2|Updated Oct 26, 2025

Search Tags:#conventional commits #release notes #semantic versioning #CHANGELOG

Ready to run

npx skills add https://github.com/matteocervelli/llms --skill changelog-generator-matteocervelli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/matteocervelli/llms/tree/main/.claude/skills/changelog-generator
Command: npx skills add https://github.com/matteocervelli/llms --skill changelog-generator-matteocervelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides the generation of CHANGELOG entries following conventional commits and semantic versioning.

Core Features & Use Cases

Conventional Commits: Classify changes by type and impact.
Semantic Versioning: Suggest version bumps (major/minor/patch).
Changelog Formatting: Produce consistent, human-friendly notes.

Quick Start

Generate a CHANGELOG entry from recent commits and PR summaries.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema

How do I generate a CHANGELOG from conventional commits?▼

Conventional commits provide a structured format for describing changes. This Skill analyzes your commits, classifies them by type (feature, fix, docs, perf, security, deprecation, breaking), determines the semantic version bump, and generates formatted CHANGELOG entries following the Keep a Changelog standard.

How do semantic versioning and conventional commits work together?▼

Conventional commits encode change impact in a standardized message format. Semantic versioning translates that impact into version numbers: breaking changes trigger major bumps, new features trigger minor bumps, and fixes trigger patch bumps. This Skill bridges both to suggest the next version automatically.

What change types can this Skill classify and document?▼

This Skill handles feature work, bug fixes, documentation updates, performance improvements, security enhancements, deprecations, and breaking changes. Each type is classified according to conventional commits conventions and rendered in the CHANGELOG with appropriate semantic version impact.

Can I use this for release notes after merging pull requests?▼

Yes. Provide recent commits and PR summaries describing features, fixes, and other changes. The Skill analyzes them, determines the next version bump, and produces a formatted release note entry ready to publish in your CHANGELOG.

Does this require existing commit history formatted with conventional commits?▼

The Skill works best with commits already following conventional commit conventions (type: description). If your commits lack this structure, you can provide PR summaries or manual change descriptions, and the Skill will classify and format them into CHANGELOG entries.

What output format does this Skill produce?▼

This Skill generates CHANGELOG entries formatted according to the Keep a Changelog standard, organized by version, change type, and date. Output is human-friendly, consistent, and ready to append to your existing CHANGELOG file.