home / skills / ehtbanton / claudeskillsrepo / changelog-generator

changelog-generator skill

safe

This skill generates a CHANGELOG.md using Keep a Changelog format and semantic versioning, providing an initial template from project context.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill changelog-generator

Review the files below or copy the command above to add this skill to your agents.

Files (2)

SKILL.md

614 B

---
name: changelog-generator
description: Generate CHANGELOG.md files following Keep a Changelog format. Triggers on "create changelog", "generate changelog", "release notes template", "version history".
---

# Changelog Generator

Generate CHANGELOG.md files following Keep a Changelog format.

## Output Requirements

**File Output:** `CHANGELOG.md`
**Format:** Keep a Changelog format
**Standards:** Semantic Versioning

## When Invoked

Immediately generate a CHANGELOG.md template.

## Example Invocations

**Prompt:** "Create changelog for project"
**Output:** Complete `CHANGELOG.md` with initial entries.

Overview

This skill generates complete CHANGELOG.md files that follow the Keep a Changelog format and align with Semantic Versioning. It creates a ready-to-use release history template that you can commit to your repository. The goal is to standardize release notes and make version history easy to maintain.

How this skill works

When triggered by phrases like “create changelog” or “generate changelog,” the skill builds a CHANGELOG.md file with sections for Unreleased and past versions using Keep a Changelog conventions. It populates standard headings (Added, Changed, Fixed, Deprecated, Removed, Security) and formats version headers according to semantic versioning. You receive a finished file you can edit with concrete entries for your next release.

When to use it

When starting a new project and you want a changelog scaffold
Before a release to prepare structured release notes
When standardizing changelog format across a team
When adopting Semantic Versioning and documented history
If you need a quick, consistent template for release documentation

Best practices

Keep the Unreleased section up to date with PRs or merge notes
Write short, actionable bullet points under the appropriate category
Bump versions following Semantic Versioning rules (MAJOR.MINOR.PATCH)
Link to issues or pull requests for important entries for traceability
Commit the CHANGELOG.md alongside release commits to keep history synchronized

Example use cases

Create an initial CHANGELOG.md for a newly open-sourced project
Generate a template changelog to collect items for the next release
Produce standardized release notes for a patch or minor release
Provide a consistent changelog file for CI/CD release pipelines

FAQ

Will the tool auto-detect past versions?

No. It creates a template and standard headers. You can copy existing release notes into the appropriate version sections manually.

Does it enforce Semantic Versioning?

It formats version headers to follow SemVer but relies on you to choose and update the correct version numbers.