Release notes
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/release-notes
Use when a version is shipping and you need release notes or an announcement that highlights impact for users, not the commit log.From its SKILL.md
npx -y skills add NSBen/skillfoundry --skill release-notesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.1 KB, 161 tokens by cl100k_base, as published. Nobody here has run it
Release Notes
When to use
Invoke this skill when tagging a release, writing a GitHub release, or announcing a change to users.
Steps
- Gather the diff/CHANGELOG since the last release and the linked issues.
- Lead with the one or two changes users will care about most.
- Use plain language: what's new, what changed, what to watch for (breaking changes).
- Add upgrade steps when behaviour or config changed.
- Keep it skimmable: short paragraphs or a bulleted list with links.
Examples
- "Draft release notes for v2.0"
- "Write a launch post for this feature"
References
Write for the reader who skipped the changelog; call out breaking changes and required actions prominently.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.