skills.rest
cautiouskurns
cautiouskurnsCOMMUNITY
Explore all skills by this author →
GitHub

changelog-updater

Create and maintain CHANGELOG.md files following Keep a Changelog standards.

Updated Aug 27, 2026
Search Tags:#changelog#semantic-versioning#release-notes#project-documentation#CHANGELOG.md#Keep-a-Changelog
One-click install
npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill changelog-updater-cautiouskurns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-updater
Source: https://github.com/cautiouskurns/Blood-and-Gold/tree/main/.claude/skills/changelog-updater
Command: npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill changelog-updater-cautiouskurns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to keep a consistent, documented history of changes. This Skill automates the creation and maintenance of CHANGELOG.md files, ensuring release notes and development progress are clearly recorded.

Core Features & Use Cases

  • Create and maintain CHANGELOG.md following Keep a Changelog standards.
  • Automatically update the Unreleased section when features are completed or bugs are fixed.
  • Generate release notes and provide a clear project history for stakeholders and reviews.

Quick Start

Add an Unreleased entry under Added to capture your latest change in CHANGELOG.md.

Frequently Asked Questions about changelog-updater

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

FAQPage Schema
Why does my team struggle to keep a consistent documented history of changes?▼

Teams struggle with consistent change documentation because manual tracking is often neglected; automating CHANGELOG.md updates ensures release notes and development progress are clearly recorded without extra effort.

How do I automatically maintain a CHANGELOG.md file for my project?▼

You can automatically maintain a CHANGELOG.md file by applying a skill that updates the Unreleased section whenever features are added or bugs are fixed, ensuring your project history stays current without manual tracking.

What is the Keep a Changelog standard for release notes?▼

The Keep a Changelog standard is a format for maintaining project documentation that records development progress, features, and bug fixes across releases to provide clear project history for stakeholders and reviews.

How do I generate release notes from semantic versioning updates?▼

You can generate release notes by maintaining a CHANGELOG.md file that follows Keep a Changelog standards, automatically capturing completed features and bug fixes in the Unreleased section before formal version releases.

Do I need any special tooling to track semantic versioning in release notes?▼

No special tooling is required to track semantic versioning in release notes; the process relies on basic text editing and adherence to semantic versioning standards within your CHANGELOG.md file.

Can I use this for software development project documentation?▼

Yes, this is designed for software development and release engineering workflows, helping teams document changes, track development progress, and maintain consistent release notes for project reviews.

Related Skills

Explore More Content & Communication Skills→
prulloacprulloac

semver-changelog

Compare HEAD with the latest SemVer tag and update CHANGELOG.md using Keep a Changelog structure.

Community
Intermediate
AlamatorAlamator

guide-recap

Format CHANGELOG.md entries into French and English social posts.

Community
Intermediate
nextcnextc
2

update-docs

Synchronize project documentation with codebase changes across CLAUDE.md, tasks.md, specs, design.md, changelog, and glossary.

Official
Advanced
cedicedi
7

changelog-generator

Generate customer-facing release notes from Git commit history.

Community
Intermediate