Does this skill support custom changelog formats?

This skill specifically follows the 'Keep a Changelog' standard (v1.0.0) to ensure maximum compatibility, readability, and consistency across development teams.

When should I trigger the update-changelog skill?

You should use it every time you complete a feature, fix a bug, change existing behavior, or remove functionality to keep your project records accurate and up to date.

What tools does this skill use to edit files?

The skill utilizes Read, Edit, Grep, and Glob tools to scan your existing changelog and precisely insert new entries into the correct sections.

How does it help with searchability?

The skill encourages writing entries that include specific keywords, CLI flags, and configuration names, making it easy for users to find relevant changes via text search.

Where does it place new entries in the file?

By default, it identifies the [Unreleased] section at the top of the file. During a release process, it can also help move those entries into a specific versioned header.

Changelog Manager

Name: Changelog Manager
Author: tettuan

bytettuan

Developer Tools

Automates the maintenance of searchable, standardized CHANGELOG.md files following the Keep a Changelog format.

About

The Changelog Manager skill streamlines project documentation by ensuring every feature, fix, and breaking change is recorded accurately and consistently. It adheres to the industry-standard 'Keep a Changelog' format, helping teams maintain a clear, user-focused history of project evolution without manual overhead. By enforcing searchable entries and proper categorization—such as Added, Fixed, and Changed—it transforms the changelog into a high-value resource for both users and contributors, ensuring that important updates never get lost in the commit history.

Key Features

Generates concise, searchable entries focused on user impact rather than implementation details.
0 GitHub stars
Supports inclusion of specific identifiers like CLI flags, config options, and command names.
Enforces standardized 'Keep a Changelog' formatting and structure.
Automatically categorizes changes into Added, Changed, Fixed, and Removed sections.
Manages the [Unreleased] section and automates version-specific release entries.

Use Cases

Standardizing documentation quality across large projects with multiple contributors.
Documenting new features or bug fixes immediately after code implementation to ensure accuracy.
Preparing project releases by transitioning [Unreleased] items to a versioned block with dates.

About

Key Features

Generates concise, searchable entries focused on user impact rather than implementation details.
0 GitHub stars
Supports inclusion of specific identifiers like CLI flags, config options, and command names.
Enforces standardized 'Keep a Changelog' formatting and structure.
Automatically categorizes changes into Added, Changed, Fixed, and Removed sections.
Manages the [Unreleased] section and automates version-specific release entries.

Use Cases

Standardizing documentation quality across large projects with multiple contributors.
Documenting new features or bug fixes immediately after code implementation to ensure accuracy.
Preparing project releases by transitioning [Unreleased] items to a versioned block with dates.