What do I need to use Changelog Generator?

Commits or release notes; Version number; Release date; Audience; Any breaking changes; Previous version behaviour (optional); Scope.

Is Changelog Generator free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Changelog Generator

Q: How do I know the Changelog Generator output is good?

The skill verifies itself against its own quality checks: Breaking changes are at the top with migration instructions; All entries are user-facing language (no internal variable names or implementation details); Related commits are grouped into single entries (not listed individually); Version and date header is correct.

🟢 Production-Ready🕐 updated 2026-07-14 🔷 SkillSpec L3 pm-engineering

Convert a git log, commit list, or release notes into a polished, user-facing changelog. Use when writing release notes, generating a CHANGELOG.md entry, or documenting what changed in a version. Produces a structured changelog section with version header, categorised changes, and migration notes. For an already-curated change list use changelog-writer instead.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸Commits or release notes — paste `git log --oneline`, raw commit messages, or a description of what changed

▸Version number — e.g. 2.4.0, v1.0.0-beta.2

▸Release date — or "today"

▸Audience — developers using an API / end users of a product / internal team — affects language

▸Any breaking changes — flag these explicitly if known

▸Previous version behaviour (optional) — optional — paste the previous changelog entry or describe what is changing; needed for accurate "Changed" entries

▸Scope — whole product / specific package or module — e.g. "payments SDK only", "iOS app", "all services"

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Breaking changes are at the top with migration instructions

✓All entries are user-facing language (no internal variable names or implementation details)

✓Related commits are grouped into single entries (not listed individually)

✓Version and date header is correct

✓Empty sections are omitted

✓No entries start with past-tense verbs (no "Added", "Fixed", "Removed" — use "Add", "Fix", "Remove")

✓Every breaking change entry includes a specific migration action (not just "update your code")

⚠️ What it refuses to do

Do not include implementation details in changelog entries — users need to know what changed for them, not how the code was refactored internally

Do not list every micro-commit as a separate entry — related commits should be grouped into one user-facing change

Do not omit the migration path for breaking changes — a breaking change entry without a specific migration action forces users to read the source code

Do not include empty sections — a "### Fixed" section with no entries signals the template was filled in carelessly

Do not write breaking changes in the same casual tone as minor additions — breaking changes must be visually prominent and call out migration requirements explicitly

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="changelog-generator"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Changelog Generator is one of 1153 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog