Changelog writer

Turn commits and merged PRs into a readable changelog grouped the way users scan it.

Install in Claude Code

Create a folder whose name matches the skill name field (changelog-writer/). Save the text below as SKILL.md inside it. Personal skills go in ~/.claude/skills/changelog-writer/. Project skills go in .claude/skills/changelog-writer/. Claude Code discovers them from the filesystem.

Upload on claude.ai

Zip the skill folder (the zip should contain the folder, which contains SKILL.md) and upload it in Claude’s Skills settings. Anthropic’s current platform docs list custom uploads on Pro, Max, Ultra, Team, and Enterprise plans when code execution is enabled. Check the Claude Help Center for the latest plan details. Read the files before you turn a skill on.

Use with the Claude API

Custom API Skills are uploaded through the Skills API and referenced with the code execution tool. Skills do not sync automatically from Claude Code or claude.ai — install this folder again on the surface where you need it. See Anthropic’s Agent Skills overview.

---
name: changelog-writer
description: Turns commit lists, merged pull requests, or release notes into a user-readable changelog grouped by added, changed, fixed, and breaking changes. Use when the user asks for a changelog, release notes, or a summary of what shipped.
---

# Changelog writer

## Goal
Write release notes a user or teammate can scan. Describe impact, not every file touch.

## Preferred grouping
Follow the spirit of Keep a Changelog:
- Added
- Changed
- Deprecated
- Removed
- Fixed
- Security

Omit empty sections. Put breaking changes first if any exist.

## Workflow
1. Read the supplied commits, PR titles, or previous notes. If a version number and date are missing, ask or use placeholders the user can fill.
2. Drop noise: merge commits, lint-only changes, version bumps that have no user meaning, and "wip" messages.
3. Combine related commits into one bullet.
4. Rewrite developer shorthand into plain language. `fix npe in billing` becomes `Fixed a crash that could occur when opening an invoice with no line items.`
5. Keep internal refactors out unless they change performance, compatibility, or operator workflow.
6. Record breaking changes with a migration hint when the source material includes one. Do not invent migration steps.

## Output template
```markdown
# [Version] — [YYYY-MM-DD]

## Breaking changes
-

## Added
-

## Changed
-

## Fixed
-

## Security
-
```

## Rules
- Do not invent features that are not in the source list.
- Do not add marketing adjectives ("delightful", "robust", "seamless").
- Ticket IDs belong at the end of a bullet only when the user supplied them: `Fixed login timeouts on slow connections (#4821).`
- If the source is too vague to be honest, list the unclear items in a `Needs author input` section instead of guessing.

You may copy and adapt this free skill for personal or commercial use. If you republish it, please credit Skillory with a link. Audit any skill — including this one — before enabling it in an environment with access to private data.

Related skills

Claude Engineering SKILL.md

Code review

Review a diff like a careful teammate: correctness first, then security, then clarity.

Open skill →

Claude Engineering SKILL.md

Git commit messages

Write conventional commit messages from a staged diff, without fluff or invented ticket IDs.

Open skill →

Claude Productivity SKILL.md

Meeting notes

Turn messy transcripts and rough notes into minutes with decisions, owners, and due dates.

Open skill →