changelog-updater

Update CHANGELOG.md with categorized changes and semantic version numbers.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/u9401066/copilot-capability-manager --skill changelog-updater-u9401066
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-updater
Source: https://github.com/u9401066/copilot-capability-manager/tree/main/.claude/skills/changelog-updater
Command: npx skills add https://github.com/u9401066/copilot-capability-manager --skill changelog-updater-u9401066

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of maintaining release notes by automatically categorizing changes and determining version numbers according to Keep a Changelog format.

Quick Start

Update the CHANGELOG.md with the latest changes following semantic versioning standards.

Frequently Asked Questions about changelog-updater

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

FAQPage Schema
How do I automate changelog updates for semantic versioning?

Automated changelog updates apply semantic versioning rules to categorize changes (Added, Changed, Deprecated, Removed, Fixed, Security) and derive version numbers (MAJOR.MINOR.PATCH), then generate Keep a Changelog compliant entries in CHANGELOG.md without manual formatting.

What is Keep a Changelog format and why use it?

Keep a Changelog is a standardized release notes format that organizes changes by category and version. It ensures consistency across projects, improves readability for users tracking project evolution, and establishes a predictable structure for parsing and automation.

How do I determine version numbers when releasing?

Version determination follows semantic versioning: MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes. Automated version mapping parses change keywords and categories to derive the correct semantic version increment without manual calculation.

Can I use this with existing CHANGELOG.md files?

Yes, the Skill updates CHANGELOG.md by applying Keep a Changelog structure to new release sections while preserving existing entries. It handles both pre-release and post-release cycles, maintaining file integrity across version cycles.

What change categories does the automation recognize?

The Skill categorizes changes into six standard types: Added (new features), Changed (behavior modifications), Deprecated (upcoming removals), Removed (deleted features), Fixed (bug repairs), and Security (vulnerability patches), matching Keep a Changelog conventions.

Does this work for pre-release and production versions?

Yes, the Skill implements formatting logic for both pre-release and post-release cycles, automatically generating Keep a Changelog compliant sections that distinguish development versions from stable releases.