release-notes
Skill130 starsChanged 11 months agoMITView on GitHub
Use when the user asks to draft release notes, changelog entries, or GitHub Release text from commits, tags, branches, or merged pull requests. Resolves an exact Git range and surfaces breaking changes, migrations, security impact, and upgrade steps.
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 145 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read repository release conventions and determine the version, audience, and exact from_ref..to_ref range.
- Distinctive: line 12
Verify both refs and record their SHAs.
- Distinctive: line 16
Use first-parent history to identify release-sized changes, then inspect the full commit list and diff so squash, rebase, and direct …
- Distinctive: line 17
Prefer the repository connector for linked PR and issue metadata.
- Distinctive: line 18
Read relevant diffs for configuration, API, schema, migration, dependency, runtime, deployment, and security changes.
- Distinctive: line 24
Call out breaking changes, prerequisites, data or configuration migrations, deprecations, security fixes, known issues, and rollback …
- Very specific: line 29
Use references/release-notes-template.md as a menu, not a requirement to include every heading.
“Common” is measured: kept by at least 6 in 10 of the 145 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
Resolve the range
- Read repository release conventions and determine the version, audience, and exact
from_ref..to_refrange. - Derive the previous release from reachable tags when unambiguous. Ask before proceeding if multiple release lines or an unknown target make the range materially ambiguous.
- Verify both refs and record their SHAs. Do not use a date window when an exact range is available.
Gather evidence
- Use first-parent history to identify release-sized changes, then inspect the full commit list and diff so squash, rebase, and direct commits are not missed.
- Prefer the repository connector for linked PR and issue metadata; use the hosting CLI or local Git as fallback.
- Read relevant diffs for configuration, API, schema, migration, dependency, runtime, deployment, and security changes. Do not infer impact from titles alone.
- Separate user-visible changes from internal maintenance and omit noise that does not help the target audience.
Write and verify
- Lead with what changed and why it matters.
- Call out breaking changes, prerequisites, data or configuration migrations, deprecations, security fixes, known issues, and rollback constraints explicitly.
- Include stable PR or issue references when available.
- Omit empty sections. Never invent verification, issue links, compatibility claims, or a release date.
- Recheck the range, diff statistics, and any migration or upgrade instruction before delivery.
Use references/release-notes-template.md as a menu, not a requirement to include every heading. Publishing a tag or hosted release requires separate explicit authorization.
Other versions159 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 159
- 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
149 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.
Used alongsideProjects 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 5 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 5 projects that use this
45ckSkillpestle-analysis
Also in 5 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 6 projects that use this
- +8 more from skytiger6724
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- branch-cleanerSkill
- bug-triageSkill
- ci-fixSkill
- commit-workSkill
- create-prSkill
- dependency-upgraderSkill
- docs-syncSkill
- focused-tddSkill
- manage-product-ideasSkill
- pr-visual-explainerSkill
- rebase-assistantSkill
- regex-builderSkill
- review-architecture-scopeSkill
- review-backend-changeSkill
- review-frontend-changeSkill
- review-security-privacySkill
- review-test-coverageSkill
- vps-checkupSkill
- write-ui-copySkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.