managing-changelog

Create and update CHANGELOG.md files using Common Changelog or Keep a Changelog standards.

Updated Nov 26, 2025

Search Tags:#automation #changelog #versioning #markdown #release #keep-a-changelog

Ready to run

npx skills add https://github.com/thoeltig/claude-code-toolkit --skill managing-changelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: managing-changelog
Source: https://github.com/thoeltig/claude-code-toolkit/tree/main/plugins/changelog/skills/managing-changelog
Command: npx skills add https://github.com/thoeltig/claude-code-toolkit --skill managing-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing CHANGELOG.md across releases is error-prone and time-consuming. This Skill creates, updates, and validates changelog entries following Common Changelog and Keep a Changelog standards, helping teams document changes consistently and predictably.

Core Features & Use Cases

Initialize a CHANGELOG.md when none exists
Add release entries with standard sections (Changed, Added, Removed, Fixed)
Update Unreleased section during development
Validate CHANGELOG.md formatting against recognized standards
Detect user intents around release notes, version history, or changelog maintenance

Quick Start

Initialize a new CHANGELOG.md for your project and then add a release entry for version 1.2.3 with a date and a short description.

Frequently Asked Questions about managing-changelog

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

FAQPage Schema

How do I maintain a CHANGELOG.md file across software releases?▼

A CHANGELOG.md documents all notable changes in your project using a standardized format. This Skill creates and updates CHANGELOG.md files following Common Changelog or Keep a Changelog standards, organizing changes by release version, date, and category (Added, Changed, Fixed, Removed, Deprecated, Security) so teams track modifications consistently.

What's the difference between Common Changelog and Keep a Changelog formats?▼

Common Changelog and Keep a Changelog are two widely adopted markdown standards for versioning release notes. Common Changelog uses categories: Changed, Added, Removed, Fixed. Keep a Changelog expands these with Deprecated and Security sections. This Skill enforces both schemas and helps you choose the right one for your project's needs.

Can I automate changelog updates when I release a new version?▼

Yes. This Skill automates creating release entries with semantic versioning, populating standard sections, and updating the Unreleased area during development. You trigger updates by referencing changelog-related terms like 'release notes', 'version history', or 'add to changelog', and the Skill handles formatting and validation.

How do I validate that my CHANGELOG.md follows the correct format?▼

This Skill includes format validation against recognized standards, checking that your CHANGELOG.md adheres to Common Changelog or Keep a Changelog structure. Validation catches inconsistencies in section headers, version formatting, and semantic versioning so your release notes remain compliant and readable.

Do I need semantic versioning to use this Skill?▼

Semantic versioning is the standard versioning scheme this Skill implements and expects. It uses MAJOR.MINOR.PATCH format (e.g., 1.2.3) to organize release entries. If your project already uses semantic versioning, integration is straightforward; the Skill enforces consistency across all changelog entries.

Can this Skill initialize a changelog for an existing project with no release history?▼

Yes. This Skill creates a new CHANGELOG.md from scratch when none exists, setting up the standard structure and sections for your project. You can then add retrospective release entries or begin tracking changes going forward using the established format.