release-notes
Skill45 starsChanged 24 days agoMITView on GitHub
Use when asked to summarize changes since the last release tag into a customer-facing release note, such as "summarize the changes since the last release", "write the release notes", or "what changed since the last version". Only for drafting the note; for publishing to Slack use announce-kit-release instead.
176 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- paulocsb/worldcup-fifa-pooltheir own version, first seen Nov 8, 2026
- OldemarJesus/connectlife-mcp-servertheir own version, first seen Nov 8, 2026
- op3616windows/skillstheir 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 versions176 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 176
- 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
166 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- announce-kit-releaseSkill
- secure-rust-dependency-changesSkill
- shared-stateSkill
- updating-artifact-schemaSkill
- user-docsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 162 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Verify the range first: resolve both endpoints with git rev-parse HEAD <tag>^{commit}, then count it with git rev-list <tag>..HEAD --count.
- Distinctive: line 14
Read the actual diff of behavior-affecting changes to state real user impact, not restated commit subjects.
- Distinctive: line 25
No internal identifiers: file paths, class/function names, line counts, PR or issue numbers, commit hashes.
“Common” is measured: kept by at least 6 in 10 of the 162 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 from Git History
- Last release tag:
git tag --sort=-creatordate | head -1. - Version number: read from
Cargo.tomlat HEAD. Never infer from tag arithmetic — merges bump the patch independently of tags. - Collect evidence:
- Verify the range first: resolve both endpoints with
git rev-parse HEAD <tag>^{commit}, then count it withgit rev-list <tag>..HEAD --count. If the count is implausibly large for one release, the range is wrong (e.g. the..HEADsuffix was lost) — stop and re-resolve instead of summarizing. - Commits with full messages:
git log <tag>..HEAD --format='%h %s%n%b' - Per-commit scope:
git show --stat <sha> - Read the actual diff of behavior-affecting changes to state real user impact, not restated commit subjects.
- Verify the range first: resolve both endpoints with
- Contributor handles:
gh api repos/<owner>/<repo>/commits/<sha> --jq .author.login— GitHub maps commit email to account. Never resolve handles by searching usernames or guessing from names; name search returns same-name strangers. - Write the note:
- Title: a one-line theme naming the release's dominant customer benefit.
- Headline features get a short expanded section with benefit bullets; everything else stays one compact bullet each. If nothing needs expansion, just list compact bullets.
- Attribute every change to
@handle. - Close with a contributors list and a compatibility statement.
Style rules (hard)
- Customer-facing: describe what the user experiences, not what the code does.
- No internal identifiers: file paths, class/function names, line counts, PR or issue numbers, commit hashes. If the user wanted git output they would use git.
- GitHub handles, never full names.
- No emojis.
- Version comes from the manifest, never from tag arithmetic.
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.