changelog-creator

Automate CHANGELOG.md updates across multi-repo projects during PR merges and releases.

2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/jackonedev/agent_skills --skill changelog-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-creator
Source: https://github.com/jackonedev/agent_skills/tree/main/skills/changelog-creator
Command: npx skills add https://github.com/jackonedev/agent_skills --skill changelog-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Keeps CHANGELOG.md files consistent and up-to-date across repositories and components, reducing manual overhead and drift in release documentation.

Core Features & Use Cases

  • Maintains an unreleased section to surface draft changes and keeps released blocks immutable.
  • Enforces a stable, cross-project category order (e.g., Added, Changed, Deprecated, Removed, Fixed, Security).
  • Auto-places new entries at the bottom of the appropriate category and moves entries during releases.
  • Supports multi-component repos by updating only the changelogs relevant to the changed components.
  • Provides templates and formatting guidance to standardize changelog entries.

Quick Start

Run the changelog automation when merging a PR or preparing a release to update the appropriate CHANGELOG.md.

Frequently Asked Questions about changelog-creator

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

FAQPage Schema
How do I keep a CHANGELOG.md consistent across multiple repositories?

To keep a CHANGELOG consistent across multiple repositories, apply standardized templates and enforce stable category order during PR merges and releases. This reduces manual overhead and prevents documentation drift.

How does changelog automation handle versioning and entry placement during releases?

Changelog automation handles versioning by maintaining an unreleased section for draft changes and keeping released blocks immutable. During releases, it auto-places entries at the bottom of appropriate categories and moves them into permanent version blocks.

Can I use this to maintain separate changelogs for different components in a monorepo?

Yes, you can maintain separate changelogs for different components in a monorepo. The automation supports multi-component repositories by detecting changes and updating only the specific CHANGELOG.md files relevant to the modified components.

What is the correct category order for a standardized changelog?

A standardized changelog enforces a stable, cross-project category order: Added, Changed, Deprecated, Removed, Fixed, and Security. This structure ensures consistent entry placement across all project documentation.

When should I run changelog automation in my development workflow?

You should run changelog automation when merging a PR or preparing a release. Running it at these stages captures draft changes in the unreleased section and finalizes version blocks accurately.