keepachangelog

Writes and maintains CHANGELOG.md files following the Keep a Changelog 1.1.0 format.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/DeepSpaceCartel/skills --skill keepachangelog-deepspacecartel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keepachangelog
Source: https://github.com/DeepSpaceCartel/skills/tree/main/skills/keepachangelog
Command: npx skills add https://github.com/DeepSpaceCartel/skills --skill keepachangelog-deepspacecartel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often treat changelogs as raw git log dumps or skip them entirely, leaving users unable to understand what changed between releases. This Skill enforces the Keep a Changelog 1.1.0 format so every release gets a clear, human-readable, linkable entry. ## Core Features & Use Cases - Structured Release Entries: Enforces the six change categories (Added, Changed, Deprecated, Removed, Fixed, Security) in the correct order, with version/date headers and reverse-chronological ordering. - Unreleased Section Workflow: Manages the [Unreleased] section at the top of the file, renaming it to the new version and date at release time. - Comparison Links & Yanked Releases: Adds per-version diff links for GitHub/GitLab and marks pulled releases with a machine-parseable [YANKED] tag. - Use Case: When preparing a v1.4.2 release, ask the AI to convert the accumulated Unreleased entries into a properly formatted ## [1.4.2] - 2026-03-14 section with categorized changes and a fresh comparison link. ## Quick Start Use the keepachangelog skill to add a new release entry for version 1.4.2 to my CHANGELOG.md based on the changes currently listed under Unreleased.

Frequently Asked Questions about keepachangelog

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

FAQPage Schema
How do I write a CHANGELOG.md in Keep a Changelog format?▼

Start with a header stating the file follows Keep a Changelog and Semantic Versioning, then add an [Unreleased] section followed by version sections in reverse-chronological order. Each version uses the header format ## [X.Y.Z] - YYYY-MM-DD with changes grouped under the six categories.

What are the six Keep a Changelog categories?▼

The six categories are Added, Changed, Deprecated, Removed, Fixed, and Security, listed in that order. Use only the categories that apply to a given version, and call out Security fixes separately even if they would otherwise read as Fixed.

How do I handle the Unreleased section when publishing a release?▼

At release time, rename the [Unreleased] header to the new version number and date, then open a fresh empty [Unreleased] section above it. Never leave the previous release's changes mixed in with the next one's.

Should I delete a changelog entry for a yanked release?▼

No, a pulled release still gets an entry marked with a [YANKED] tag after the date, such as ## [0.4.1] - 2026-01-09 [YANKED]. Deleting it erases the record of what happened, while the tag stays both human-visible and machine-parseable.

Can I just paste git commit messages into my changelog?▼

No, changelogs are written for humans, not as a dump of git log. Each entry should describe the observable effect on someone using the software, not the internal diff or raw commit subjects.