changelog-generator

Generate Keep a Changelog 1.1 compliant changelogs from Conventional Commits.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill changelog-generator-robotijn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/robotijn/ctoc/tree/main/skills/documentation/changelog-generator
Command: npx skills add https://github.com/robotijn/ctoc --skill changelog-generator-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually maintaining changelogs leads to inconsistent formatting, missed breaking changes, incorrect semantic version bumps, leaked internal commit noise, and non-compliance with the Keep a Changelog 1.1 standard that users and automated tools depend on for release visibility.

Core Features & Use Cases

  • Conventional Commits Parsing: Automatically categorizes commit types (feat, fix, breaking change, etc.) into the correct Keep a Changelog 1.1 sections and derives the appropriate semver bump.
  • Breaking Change Enforcement: Surfaces all breaking changes with mandatory migration guides to prevent user upgrade failures, and blocks releases if required entries are missing.
  • Use Case: For a team preparing a v3.0.0 release, this skill scans commits since the last tag, flags the removed legacy /api/v1 endpoint as a breaking change with a before/after migration snippet, excludes internal chore and CI commits, and drafts a compliant changelog for human review before publishing.

Quick Start

Use the changelog-generator skill to draft a compliant changelog for your next release from your project's recent commit and PR history.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I auto-generate changelogs from conventional commits?

To auto-generate changelogs from conventional commits, this skill parses your git commit history and PR descriptions, categorizing types like feat and fix into Keep a Changelog 1.1 sections and deriving the correct semver bump.

How does semver bump derivation work for breaking changes?

Semver bump derivation for breaking changes works by parsing conventional commits to detect breaking changes, which triggers a major version bump and enforces mandatory migration guides to prevent upgrade failures.

Can I filter internal-only commits from public release notes?

You can filter internal-only commits from public release notes because this skill automatically excludes internal chore and CI commits, ensuring only public-facing changes appear in the final changelog output.

Does this changelog generator work for monorepos and CI/CD pipelines?

This changelog generator works for monorepos, multi-language codebases, and automated CI/CD release pipelines, applying to all versioned software projects using conventional commits to draft compliant release notes.

What is the best way to enforce Keep a Changelog 1.1 formatting?

The best way to enforce Keep a Changelog 1.1 formatting is to use an automated generator that structures categorized conventional commits into compliant sections and blocks releases if required breaking change entries are missing.

Why does my manual release process miss breaking change migration guides?

Manual release processes miss breaking change migration guides due to human error, which this skill prevents by surfacing all breaking changes and blocking releases until mandatory migration snippets are provided.