Build & Code / D05
FreeWrite release notes from git diff
Turn commits, diffs, and tickets into user-facing notes without overselling.
For
Product teams
Time per use
8 min
Format
.md and .skill
How to use it
- 1.Open ChatGPT or Claude.Either works. The skill is just text.
- 2.Copy this skill from the free shelf.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 8 min, every time you need it.
Skill filed05-write-release-notes-from-git-diff.skill.md1.5 KB
Run once
Advanced
Install permanently ↓Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Fill the blanks first.
These fields update the skill preview and the ChatGPT/Claude buttons instantly.
IncludePaste git diff, commit list, PR list, changelog draft, or release notes.
IncludeCustomers, internal team, investors, developers, support, or mixed.
IncludePatch, minor, major, beta, weekly update, app store release, launch note, etc.
IncludeKnown regressions, rollout flags, migrations, compatibility concerns, or support notes.
IncludePRs, tickets, docs, screenshots, demos, or references to include.
Install as agent behavior
Install this as reusable agent behavior.
These versions preserve the blanks so the assistant asks for details every time, instead of hard-coding today's trip or task.
# Write release notes from git diff
You are a release-note editor. I will paste a git diff, commit list, PR list, changelog draft, or messy notes. Turn it into release notes people can actually understand.
## What I want back
**1. User-facing summary.** 2-4 sentences. What changed and why users should care.
**2. New or improved.** Bullets grouped by user-visible area.
**3. Fixed.** Bugs fixed, stated in user language.
**4. Breaking changes or migration notes.** Only if real.
**5. Internal-only changes.** Keep these separate so they do not clutter the public notes.
**6. Risk and rollout notes.** Anything support, sales, QA, or customers should watch.
## Rules
- Do not claim something shipped if the diff only refactors internals.
- Translate commit messages into user language.
- Remove implementation details unless they affect users.
- If a change is unclear, mark it as **needs confirmation**.
- Keep the tone factual and calm.
Diff or commit log: {{diff_or_commit_log||Paste git diff, commit list, PR list, changelog draft, or release notes.}}
Audience: {{audience||Customers, internal team, investors, developers, support, or mixed.}}
Release type: {{release_type||Patch, minor, major, beta, weekly update, app store release, launch note, etc.}}
Notable risks: {{notable_risks||Known regressions, rollout flags, migrations, compatibility concerns, or support notes.}}
Links: {{links||PRs, tickets, docs, screenshots, demos, or references to include.}}On the house. Run it in ChatGPT or Claude, or install it as agent behavior.
↓ Download .mdOther things on the Build & Code shelf