changelog-manage

Add categorized entries to CHANGELOG.md and calculate semantic version bumps.

5|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/no-problem-dev/claude-code-plugins --skill changelog-manage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-manage
Source: https://github.com/no-problem-dev/claude-code-plugins/tree/main/plugins/release-flow/skills/changelog-manage
Command: npx skills add https://github.com/no-problem-dev/claude-code-plugins --skill changelog-manage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of adding entries to your CHANGELOG file and calculating semantic version bumps, ensuring your project's release notes are always up-to-date and consistent.

Core Features & Use Cases

  • Add CHANGELOG Entries: Easily add new features, changes, bug fixes, or security updates to the "Unreleased" section of your CHANGELOG.md.
  • Version Calculation: Automatically determine the next semantic version (major, minor, patch) based on the type of changes made.
  • Use Case: After implementing a new feature and fixing a bug, use this Skill to add both to your CHANGELOG and then bump the version from 1.2.3 to 1.3.0.

Quick Start

Add a new feature to the changelog with the description "Implemented user profile editing".

Frequently Asked Questions about changelog-manage

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

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

You can automate changelog entries by adding categorized updates like Added or Fixed to the Unreleased section, which then calculates the appropriate semantic version bump for your software release.

How does semantic version bump calculation work with git tags?

Semantic version bump calculation works by parsing your CHANGELOG.md and Git tags to determine the next major, minor, or patch increment based on the categorized changes you have logged.

How do I add a new feature to the unreleased section of a CHANGELOG?

To add a new feature to the unreleased section, you input the description of the update, and the entry is categorized under Added or Changed to prepare for the next version calculation.

Do I need Git tags to calculate the next software version?

Yes, you need Git tags because the version calculation requires parsing them alongside your CHANGELOG.md to accurately determine the next major, minor, or patch increment.

Can I categorize bug fixes and security updates separately in release notes?

Yes, you can categorize bug fixes and security updates separately in release notes by adding distinct entries under categories like Fixed or Security within the Unreleased section of your CHANGELOG.

What is the best way to manage release notes for consistent versioning?

The best way to manage release notes for consistent versioning is to automate the addition of categorized CHANGELOG entries and calculate semantic version bumps directly from your Git tags.