changelog-generator

mohitagw15856/pm-claude-skillsVersion ControlAudit passedSnapshot 7d89e59cb1a8

Installs: 0

Summary

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.

SKILL.md

Changelog Generator Skill

Converts raw git commits, a diff summary, or developer release notes into a polished changelog entry — categorised, user-facing, and following Keep a Changelog conventions.

Required Inputs

Ask for these if not provided:

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 — 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")

Output Format

Follow Keep a Changelog format:

[X.Y.Z] — YYYY-MM-DD

Breaking Changes ⚠️

[Only include if there are breaking changes]

[Breaking change]: [What changed and what it breaks]
Migration required: [Specific action the user must take]

Added

[New feature or capability, written from the user's perspective]
[Another addition]

Changed

[Changed behaviour — what it did before vs. what it does now]
[Performance improvement with measurable impact if known]

Dimension	0	5	10
Reader-facing translation	Entries restate commit messages, with internal identifiers and implementation details	Mostly user-facing, but a few entries leak internals or describe the patch rather than what was broken	Every entry describes the change from the reader's perspective — what changed for them, never how the code was refactored
Breaking-change handling	Breaking changes buried mid-list or missing a migration path	Flagged at the top, but migration guidance is vague ("update your code")	At the top with ⚠️, each with a specific migration action the user can execute
Curation & grouping	Every micro-commit listed; internal-only commits included	Some grouping, but related commits still appear as separate entries or noise slips through	Related commits grouped into single entries; internal-only commits excluded; nothing a user can't observe
Format discipline	Wrong or missing version/date header; past-tense verbs; empty sections left in	Header correct but tense or empty-section slips remain	Keep a Changelog conventions throughout — correct header, imperative mood, only populated sections

changelog-generator

Summary

SKILL.md

Changelog Generator Skill

Required Inputs

Output Format

[X.Y.Z] — YYYY-MM-DD

Breaking Changes ⚠️

Added

Changed

Fixed

Deprecated

Removed

Security

Formatting Rules Applied

Deeper Materials

Scoring Rubric (0–40)

Quality Checks

Anti-Patterns

Usage Examples

Related skills