release-notes
Skill0 starsChanged 5 days agoMITView on GitHub
Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal.
181 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- 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
- ychampion/ystacktheir own version, first seen Nov 15, 2026
- facebook/bpfiltertheir own version, first seen Nov 9, 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 versions181 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 181
- 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
- formbricks/formbricks★ 13ksame name
171 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codebase-designSkill
- desloppifySkill
- domain-modelingSkill
- grill-meSkill
- makefile-generatorSkill
- proseSkill
- pyproject-generatorSkill
- repo-bootstrapSkill
- researchSkill
- retroSkill
- to-specSkill
- to-ticketsSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
1
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 23
Write to "you". Warm, plain words, no hype, no superlatives, no jargon.
“Common” is measured: kept by at least 6 in 10 of the 167 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
Turn the newest released changelog version into notes a reader with no technical background understands and cares about. The changelog stays technical; the notes translate it.
Discover the convention first
Find how this repository publishes notes before writing: a RELEASE_NOTES.md, a docs/releases/ folder, GitHub or GitLab releases, or nothing yet. Read one existing entry and follow its structure. With no established destination, ask the user where the notes go and do not invent one.
Source of truth
Work only from the changelog section for the version being released. Every claim in the notes traces to a line in it. No invented features, no numbers the changelog does not contain, no promises about the future.
Voice
Write to "you". Warm, plain words, no hype, no superlatives, no jargon. Say what the reader can now do, not what the code does. A sentence the reader cannot act on or picture does not belong.
Shape
Open with two or three sentences of prose carrying the release's point. Group the rest under headings the reader recognizes (what is new, what changed, what got fixed). End with a "Good to know" section for behavior changes, requirements and caveats the reader must act on.
Translate
Each technical change becomes the reader's outcome. Use the project's own words for features. When a term cannot be avoided, give it one plain sentence of meaning in place, the first time it appears. Read the result aloud once; anything you cannot say without slowing down is not done.
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.