changelog-generator

Generate and maintain CHANGELOG.md files using Keep a Changelog templates.

4|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill changelog-generator-tomada1114
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-generator
Source: https://github.com/tomada1114/tomada-claude-plugins/tree/main/claude-dev-kit/skills/claudecode-skill-creating/examples/4-skill-with-templates
Command: npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill changelog-generator-tomada1114

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create and maintain professional CHANGELOG.md files following the Keep a Changelog format. Demonstrates the use of templates for consistent output.

Core Features & Use Cases

  • Create and update CHANGELOG.md files for projects using the Keep a Changelog structure.
  • Apply release templates to document new versions, including Added/Changed/Removed/Fixed/Security sections.
  • Follow best practices like semantic versioning, Unreleased sections, and migration notes.

Quick Start

Use the changelog-generator skill to create a new CHANGELOG.md and initialize it with an Unreleased section using the provided templates.

Frequently Asked Questions about changelog-generator

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

FAQPage Schema
How do I automatically generate and maintain a CHANGELOG.md file?

Changelog-generator creates and updates CHANGELOG.md files following the Keep a Changelog format with structured templates. It organizes changes into Unreleased sections and category blocks (Added, Changed, Deprecated, Removed, Fixed, Security) for consistent, professional documentation across releases.

What is the Keep a Changelog format and why should I use it?

Keep a Changelog is a standardized format for documenting software changes by version and category, making release notes human-readable and machine-parseable. It pairs with semantic versioning to help users and developers understand what changed and why between releases.

Can I use templates to keep my changelog entries consistent?

Yes, changelog-generator uses templates to ensure consistent output structure across all entries. Templates enforce the same sections, wording patterns, and formatting so every release follows the same professional standard without manual reformatting.

How do I document new releases with semantic versioning in my changelog?

Changelog-generator applies release templates that structure version entries with semantic versioning notation and populate category sections (Added, Changed, Fixed, Security). This ensures each version release follows a predictable format tied to version numbers and change types.

What's the best way to organize software changes across multiple releases?

Keep a Changelog organizes changes by version and category type, making it easy to scan what happened in each release and why. Changelog-generator maintains this structure automatically, separating unreleased work from published versions for clarity.

Do I need to manually format migration notes in my changelog?

Changelog-generator supports optional migration notes within its Keep a Changelog structure, allowing you to document breaking changes and upgrade paths. Templates keep these notes formatted consistently with the rest of your changelog.