changelog

Create or update CHANGELOG.md following Keep a Changelog formatting guidelines.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rodacato/kwik-e-dev --skill changelog-rodacato
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/launchpad/skills/changelog
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill changelog-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a clean, accurate release history by creating or updating CHANGELOG.md in Keep a Changelog format, so teams have a trustworthy narrative of changes across versions.

Core Features & Use Cases

  • Create or update CHANGELOG.md following Keep a Changelog format to document releases.
  • Initialize and maintain an [Unreleased] section, and populate versioned entries as releases occur.
  • Align with the releasing workflow to ensure release notes are ready before shipping.

Quick Start

Run the changelog skill to create or update CHANGELOG.md in Keep a Changelog format.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate CHANGELOG.md updates for project releases?

To automate CHANGELOG.md updates, you can run the changelog skill to create or update your release history in Keep a Changelog format. It initializes an [Unreleased] section and populates versioned entries as releases occur.

What is the Keep a Changelog format for maintaining release notes?

The Keep a Changelog format is a structured guideline for maintaining release notes in a CHANGELOG.md file. It ensures teams have a trustworthy narrative of changes by documenting releases with proper version entries and comparison links.

How do I backfill an initial changelog across previous versions?

You can backfill an initial changelog across previous versions by running the changelog skill. It applies to projects preparing a release or backfilling history, structuring past version entries according to Keep a Changelog formatting guidelines.

Does this changelog automation work with my existing releasing workflow?

Yes, the changelog automation integrates with your releasing workflow to ensure release notes are ready before shipping. It aligns with your release process to guarantee proper version entries and comparison links are generated.

What's the best way to maintain an [Unreleased] section in release documentation?

The best way to maintain an [Unreleased] section is to use the changelog skill, which initializes and continuously updates this section. It populates the section with versioned entries as releases occur, keeping your documentation accurate.