release-notes
Skill4 starsChanged 2 days agoMITView on GitHub
Write release notes for users, not developers, from git history between two versions: read the commits and PRs, drop what users can't see, group the rest by what changed for them, and write each line as a plain-language benefit, with breaking changes and required actions first. Use for "write release notes", "changelog for v2.3", "what's new since the last release", "draft the update post", or before tagging a release.
180 other projects use a version of this.
Adopted by
Most recently taken up by
- binay-py/claude-skillstheir own version, first seen Nov 15, 2026
- viscouslofi/wolfpacktheir own version, first seen Nov 15, 2026
- WireCatLabs/wirecat-desktoptheir own version, first seen Nov 15, 2026
- facebook/bpfiltertheir own version, first seen Nov 9, 2026
- openfrontio/OpenFrontIOtheir own version, first seen Nov 8, 2026
- microsoft/agent-frameworktheir own version, first seen Nov 8, 2026
Used with
Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 6 projects that use this
- skytiger6724Skill
brainstorm-ideas-new
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Also in 6 projects that use this
45ckSkillpestle-analysis
Also in 6 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 6 projects that use this
- About-IntelligenceSkill
product-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 6 projects that use this
- +7 more from skytiger6724
Other versions180 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 180
- tw93/Mole★ 74ksame name
- makeplane/plane★ 62ksame name
- tabler/tabler★ 42ksame name
- pnpm/pnpm★ 37ksame name
- quasarframework/quasar★ 27ksame name
- dotnet/core★ 22ksame name
- zauberzeug/nicegui★ 16ksame name
- adobe/react-spectrum★ 16ksame name
- espanso/espanso★ 15ksame name
- microsoft/agent-framework★ 15ksame name
170 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- agent-writingSkill
- arenaSkill
- blast-radiusSkill
- bun-playwright-runner-selectionSkill
- cinematic-shotSkill
- clean-ui-shotSkill
- codebase-designSkill
- debug-loopSkill
- dep-upgradeSkill
- diagnosing-bugsSkill
- discoverSkill
- domain-modelingSkill
- earshotSkill
- eval-judgeSkill
- flaky-testSkill
- grillingSkill
- grillSkill
- idea-scoutSkill
- improve-codebase-architectureSkill
- interrogateSkill
- make-mediaSkill
- migrate-to-rustSkill
- migration-planSkill
- multi-agent-windows-hazardsSkill
- perf-loopSkill
- postmortemSkill
- prototypeSkill
- prSkill
- real-soundSkill
- recallSkill
- repo-mapSkill
- researchSkill
- retroSkill
- secure-diffSkill
- sellSkill
- subagent-report-recoverySkill
- tasteSkill
- taste-skillSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- wayfinderSkill
- weeklySkill
- windows-bash-backslash-halvingSkill
- wizardSkill
- writing-for-agentsSkill
- ycSkill
- ystack-upgradeSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 166 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Commit messages are written for the people who wrote the code.
- Distinctive: line 36
When a commit message is unclear, read its diff.
- Distinctive: line 65
Leave out empty sections. Put the single most important change first in its section.
- Distinctive: line 70
Every line traces to at least one commit or PR (keep the mapping in your working notes, not in the output).
- Distinctive: line 78
No hype words ("blazing", "revolutionary", "seamless").
- Distinctive: line 79
Don't publish or tag; hand the draft to the user.
“Common” is measured: kept by at least 6 in 10 of the 166 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release notes
Commit messages are written for the people who wrote the code. Release notes are for the people who use it. The job is to translate, and to leave out everything they don't need.
Procedure
1. Find the range
The last release tag to now (git describe --tags --abbrev=0), or the range the user gives. List
commits with git log <from>..<to> --no-merges --format='%h %s'. Where the project uses pull requests,
read their titles and descriptions too (gh pr list --state merged --search "merged:>=<date>"); they
explain why.
2. Sort every change
| Bucket | Goes in the notes? |
| Breaking: users must change something | Yes, first, with what to do |
| New: something users can now do | Yes |
| Improved: faster, clearer, easier | Yes, if a user would notice |
| Fixed: a bug users could hit | Yes, described by the symptom |
| Security fix | Yes, as "security fix in <area>"; no exploit detail before users can patch |
| Internal: refactors, tests, CI, deps, docs typos | No |
When a commit message is unclear, read its diff. Don't guess.
3. Write each line as a user outcome
- Lead with what the user can do or will notice, not what the code does.
- Developer: "Refactor export pipeline to stream rows."
- User: "Exports of large projects no longer time out."
- Plain words. No internal names, ticket numbers or file paths unless users see them.
- A fix names the symptom the user saw: "Fixed: the app no longer logs you out after 10 minutes."
- One line each. Merge several commits that make one user-visible change into one line.
4. Assemble
## <version> - <date>
**Action needed**
- <breaking change>: <what to do, with the exact setting or command>
**New**
- ...
**Improved**
- ...
**Fixed**
- ...Leave out empty sections. Put the single most important change first in its section. If the project has an existing CHANGELOG or release format, follow it instead.
5. Check
Every line traces to at least one commit or PR (keep the mapping in your working notes, not in the output). Nothing claims more than the code does. Read it as a user who never saw the code: would they know what changed and whether they need to act?
Rules
- Users first: drop anything they can't see or act on.
- Breaking changes always come with the action to take.
- No hype words ("blazing", "revolutionary", "seamless").
- Don't publish or tag; hand the draft to the user.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.