Release Notes Composer
$1.99OfficialUse when a diff, commit log, or changelog must become polished release notes tailored to end users, developers, or internal stakeholders.
What you get
- ✓9-step procedure
- ✓1 ready-to-run code block
- ✓8-point quality checklist
- ✓8 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 5 min read
- Requires
- Works with any modern AI assistant
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes
Preview
When to use
Use this skill when the user has raw change material — a git diff, commit log, merged PR list, or an existing changelog — and needs release notes for a specific audience. Trigger on requests like 'write release notes for v2.3', 'summarize what changed since the last tag', or 'turn this changelog into a customer announcement'.
Do not use for a single-change announcement (write it directly) or for internal sprint summaries where a bullet list of PR titles is acceptable.
Inputs to gather
- The release range: previous tag and target ref. If not given, detect the last tag with
git describe --tags --abbrev=0and useLAST_TAG..HEAD. - The audience: end users, developers an
…
🔒 Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.