changelog

Create and manage Keep a Changelog entries via CLI commands.

5|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/schpet/toolbox --skill changelog-schpet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/schpet/toolbox/tree/main/plugins/changelog/skills/changelog
Command: npx skills add https://github.com/schpet/toolbox --skill changelog-schpet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and maintenance of CHANGELOG.md files by ensuring entries follow the Keep a Changelog format and by simplifying release notes and Git-history synchronization.

Core Features & Use Cases

  • Create and categorize changelog entries (added, changed, fixed, etc.) via the changelog add command.
  • Release versions and manage Unreleased vs. published sections with changelog release and version commands.
  • Review and align commits with changelog entries using changelog review, ensuring accurate documentation.

Quick Start

Use a simple command to add an entry, for example: changelog add --type fixed "resolve issue with release notes formatting"

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate changelog management from the command line?

Automate changelog management by running CLI commands like 'changelog add' to categorize entries and 'changelog release' to publish versions, keeping your project changelog up to date programmatically.

How do I keep a changelog formatted correctly for features and fixes?

To keep a changelog formatted correctly, the CLI guides entry creation into categories like added, changed, and fixed, ensuring your CHANGELOG.md adheres to the Keep a Changelog format standards.

Can I sync Git commit history with my changelog entries?

Yes, you can sync Git history with your changelog using the 'changelog review' command, which reviews and aligns commits with changelog entries to ensure accurate release documentation.

What is the best way to track unreleased changes before publishing a release?

The best way to track unreleased changes is using the 'changelog release' command, which manages the transition of entries from the Unreleased section into published version sections.

Do I need any specific dependencies to use a CLI for release management?

No specific dependencies are required to use this CLI for release management, as it operates independently to guide changelog entry creation, release tracking, and commit review.