changelog

Automate CHANGELOG.md updates with validated entries under Unreleased sections.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/mcsdodo/kniha-jazd --skill changelog-mcsdodo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/mcsdodo/kniha-jazd/tree/main/.claude/skills/changelog-skill
Command: npx skills add https://github.com/mcsdodo/kniha-jazd --skill changelog-mcsdodo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeping CHANGELOG.md up to date with user-visible changes can be tedious and error-prone. This skill automates and standardizes the process, ensuring releases are properly documented.

Core Features & Use Cases

  • Automatically appends user-facing change entries under the Unreleased section, with sections for Added, Changed, Fixed, and Removed (Pridane, Zmenene, Opravene, Odstranene).
  • Enforces a consistent, reviewer-friendly format across projects and teams.
  • Supports quick start workflows for post-release updates and audit-ready documentation.

Quick Start

Add a changelog entry for the latest release using a single, clear description.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate updating a changelog with user-visible changes?

You can automate updating a changelog by using a skill that appends user-facing entries under an Unreleased section. It validates and formats entries for Added, Changed, Fixed, and Removed categories before committing.

What is the best way to keep CHANGELOG.md consistent across software releases?

The best way to keep CHANGELOG.md consistent is to enforce a standardized, reviewer-friendly format for unreleased changes. This ensures all feature releases and bug fixes follow the same documentation rules automatically.

How do I format unreleased changelog entries for feature releases and bug fixes?

Format unreleased changelog entries by sorting user-visible changes into Added, Changed, Fixed, and Removed sections. The changelog skill automates this formatting and validates entries before they are committed.

Does the changelog automation workflow support Slovak section titles?

Yes, the changelog automation workflow supports Slovak section titles such as Pridane, Zmenene, Opravene, and Odstranene. It enforces these specific titles alongside standard Unreleased section formatting.

Can I validate changelog entries before committing them to the repository?

Yes, you can validate changelog entries before committing. The workflow checks that user-visible changes match the required formatting and section rules described in its documentation before allowing a commit.

When do I need to use an automated changelog generation process?

You need an automated changelog generation process when keeping track of user-visible changes becomes tedious and error-prone. It is applicable for post-release updates to ensure audit-ready documentation across software projects.