Notes about what changed for the customer, not what changed in the code.
Customer-readable release notes built from your commit log, tickets, or pull request titles, with breaking changes at the top.
Release notes are often a commit log with the hashes removed. 'Refactor sync queue' tells a customer nothing, and the one change that needs their action sits on line nine of a long list.
Release Notes sorts every change, drops the internal ones, and rewrites each as what you can now do or what no longer breaks. It leads with the change most users will notice, puts anything needing action first, and checks the result against the source so nothing claims more than shipped.
What it produces.
- →A lead paragraph for the change that matters most
- →A needs-attention section with dates and what to do
- →New, Improved, and Fixed lists in plain language
- →A list of what was dropped as internal, so you can overrule it
- ✦Product managers who ship every sprint or month
- ✦Engineers who write the notes because no one else will
- ✦Founders sending update emails to their users
- →release-notes.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to
~/.claude/skills/ - →release-notes-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
- →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
What it does with a real question.
I'm the support lead at Tallyboard, a scheduling app for dental offices, and we're shipping version 4.2 on March 18. Below are 23 merged PR titles and 9 Zendesk tickets from the last month, including the recurring-appointment fix, faster calendar load, and the new SMS reminder templates. Can you turn this into release notes for office managers?
Lead with the recurring-appointment fix. For an office manager, that is the change they will actually feel, because a broken recurring series means a hygienist's chair sits empty or a patient gets double-booked. Faster calendar load comes second, since it affects everyone every morning but nobody was complaining about it loudly. SMS reminder templates come third as the new capability, and I would give it one concrete line about what a manager can now do, such as setting a standard confirmation message for the whole practice instead of retyping it.
Notice what you did not give me: any breaking change. Before publishing, scan the 23 PR titles for anything touching permissions, integrations, billing, or removed settings. If a reminder default changed, or an old template format stopped working, that goes in a "needs attention" block above everything else with a date and an action. A manager who discovers that on a Monday morning will remember it longer than any fix.
Translate your Zendesk tickets into user language too. "Recurring series skipped the 29th of the month" is better than "date rollover bug." If several tickets describe the same symptom, name it once as fixed and group the minor ones into a single line. Drop the refactors and dependency bumps entirely.
Next move: draft the lead paragraph on recurring appointments in two sentences, using the exact symptom your tickets describe, and check it against the PR that fixed it so the notes claim nothing beyond what shipped on March 18.
The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.
Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.
No subscription · free updates within v1.x
Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable
Before you buy.
How is this different from just asking Claude directly?
Asked cold, Claude usually restates the commit messages in friendlier words and keeps their internal vocabulary. This translates each item into its effect on the user, pulls breaking changes to the top, and compares the draft with your list so it never promises more than you shipped.
How is this different from a Tool?
Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.
Will this work with ChatGPT, Gemini, and other LLMs?
Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.
Can I share this with my team?
It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.
What if it doesn't work for me?
If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.