update-changelog

Generate Keep a Changelog compliant CHANGELOG.md entries with categories and semantic versioning.

2|1|Updated Mar 18, 2026

Search Tags:#automation #changelog #versioning #documentation #release-notes #keepachangelog #entry-management

Ready to run

npx skills add https://github.com/harshitsinghbhandari/domain-expansion --skill update-changelog-harshitsinghbhandari

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/harshitsinghbhandari/domain-expansion/tree/main/skills/update-changelog
Command: npx skills add https://github.com/harshitsinghbhandari/domain-expansion --skill update-changelog-harshitsinghbhandari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation and maintenance of a Keep a Changelog formatted CHANGELOG.md, ensuring changes are documented for users when features are added, bugs are fixed, or releases occur.

Core Features & Use Cases

Structured entries: Automatically categorize changes into Added, Changed, Deprecated, Removed, Fixed, and Security.
Versioning and order: Maintain semantic versions and reverse chronological ordering to reflect release progress.
Consistency and governance: Enforce Unreleased section presence and user-facing language to improve release notes quality.
Use Case: When preparing a release, generate a well-formed CHANGELOG.md entry that summarizes new features and fixes for users.

Quick Start

Add a new changelog entry for your latest release with an appropriate category and version tag.

Frequently Asked Questions about update-changelog

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

FAQPage Schema

How do I automatically generate a changelog for semantic versioning releases?▼

To automatically generate a changelog for semantic versioning, this skill structures entries into standard categories like Added, Changed, and Fixed, while enforcing reverse chronological order and an Unreleased section for clear release notes.

What is the best way to maintain a Keep a Changelog formatted CHANGELOG.md?▼

The best way to maintain a Keep a Changelog format is by automating entry creation during feature additions or bug fixes, which enforces standard categories, user-facing wording, and correct versioning for consistent documentation.

How do I add structured entries to an Unreleased section in release notes?▼

You add structured entries to an Unreleased section by applying changes through this skill, which automatically categorizes updates into Added, Changed, Deprecated, Removed, Fixed, or Security before a formal release.

Does this changelog automation enforce reverse chronological order and semantic versioning?▼

Yes, this changelog automation enforces reverse chronological order and semantic versioning, ensuring newly added features and bug fixes appear correctly structured alongside previous release notes.

When do I need to use standard categories like Deprecated and Security in a changelog?▼

You need standard categories like Deprecated and Security in a changelog when documenting deprecations or vulnerability patches, ensuring user-facing release notes remain precise and compliant with Keep a Changelog standards.

Can I use this for preparing structured release notes from bug fixes and feature additions?▼

Yes, you can use this for preparing structured release notes, as it automatically summarizes bug fixes and feature additions into categorized, user-facing wording suitable for versioned releases.