What it does
Takes a changelog, commit list, or ticket list of what shipped and rewrites it in plain language grouped into new features, improvements, and bug fixes, dropping internal-only changes that users wouldn't notice or care about. Adds a short one-paragraph summary at the top for people who won't read the full list.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/release-notes-writer/ (or ~/.claude/skills/release-notes-writer/ for all projects)
GitHub Copilot (VS Code)
.github/skills/release-notes-writer/
OpenAI Codex
.codex/skills/release-notes-writer/
Cursor
.cursor/skills/release-notes-writer/ (or ~/.cursor/skills/release-notes-writer/ globally)
Compatibility
Any WordPress site; works from a plain changelog, commit log, or issue tracker export, no special plugin required.
The complete SKILL.md for this skill:
---
name: release-notes-writer
description: Use when a user wants a changelog or list of shipped changes turned into user-facing release notes, or asks to "write release notes" or "draft a changelog post".
---
# Release Notes Writer
## When to use
A set of changes just shipped and the user needs them rewritten as plain-language release notes for actual users, rather than the raw commit or ticket list.
## Procedure
1. Read the raw change list, commits, tickets, or changelog entries, in full before drafting anything.
2. Sort each item into New, Improved, or Fixed, and drop purely internal changes users wouldn't perceive.
3. Rewrite each remaining item in plain, user-facing language describing what changed for the user, not the implementation.
4. Write a 2-3 sentence summary paragraph at the top highlighting the most user-relevant change.
5. Flag any change that might need a screenshot or short video to explain, since text alone won't land it.
## Guardrails
- Don't invent user-facing benefit language for a purely technical change, leave it out rather than dressing it up.
- Keep security fixes described honestly but without exact exploit details that could help bad actors.