writing-release-notes
Skill1 starsChanged 28 days agoMITView on GitHub
Drafts customer-facing release notes from merged PRs and commit messages in the house style. Use when the user asks for release notes, a changelog, "what shipped", or a launch announcement for a version.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/vscode-documentdbtheir own version, first seen Nov 6, 2026
- pvliesdonk/markdown-vault-mcptheir own version, first seen Nov 2, 2026
- pvliesdonk/scholar-mcptheir own version, first seen Oct 31, 2026
- pvliesdonk/paperless-mcptheir own version, first seen Oct 31, 2026
- osmontero/opencode-skillstheir own version, first seen Oct 27, 2026
- it-bens/cc-porttheir own version, first seen Oct 25, 2026
Used with
Projects with it also use applying-template-updates, authoring-issues-prs 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.
pvliesdonkSkillapplying-template-updates
Use when asked to work through, apply, resolve or review a template update pull request (the weekly `copier/update` branch opened by the copier-update workflow), after running `copier update --trust` by hand, or when a template update looks like it leaves no room for something this project needs.
Also in 3 projects that use this
pvliesdonkSkillauthoring-issues-prs
Use when filing a bug, opening or creating a GitHub issue, drafting an epic or ticket, writing up a finding or review observation worth tracking, sizing a change before coding, or opening a pull request for this repository. Routes the change to the right repo first (library / template / domain), picks the right issue form, sizes the change to one PR, links epic children as native sub-issues, and applies CONTRIBUTING.md before anything is posted.
Also in 3 projects that use this
zpower426Skillroadmapping
Communicate the product evolution timeline and key milestones, balancing long-term goals with short-term delivery.
Also in 3 projects that use this
quocldSkilllogging-standard
Use when writing or reviewing code that logs, when creating or changing a logger, request or job correlation, or log redaction, and when the user says "setup log", "setup logger", "thêm log", "chuẩn hoá log", "log bị lộ token", "log quá nhiều", "review log".
Also in 3 projects that use this
nilecuiSkillwriting-documentation
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
Also in 3 projects that use this
- +7 more from pvliesdonk
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- stanfordnlp/dspy★ 39ksame name
- actualbudget/actual★ 30ksame name
- pvliesdonk/markdown-vault-mcp★ 38same name
- microsoft/vscode-documentdb★ 33same name
- osmontero/opencode-skills★ 15same name
- it-bens/cc-port★ 6same name
- pvliesdonk/scholar-mcp★ 3same name
- pvliesdonk/paperless-mcp★ 1same name
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 repositoryOne other file it gives its agents.
- templates/CLAUDE.mdCLAUDE.md
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 8 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 24
No internal ticket numbers.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Writing release notes
Inputs
- Version tag and date.
- List of merged PRs since the last tag: run
scripts/list_prs.sh <last-tag>.
Workflow
Copy and tick off:
- [ ] 1. Gather PRs (run the script; do not read git log manually)
- [ ] 2. Group: Features / Improvements / Fixes / Breaking
- [ ] 3. Rewrite each item for a customer (what they can now do, not what we changed)
- [ ] 4. Flag anything Breaking with a migration note
- [ ] 5. Validate: `scripts/check_notes.py notes.md` must print OKStyle
- Lead with the benefit. "You can now export to CSV" not "Added CSV exporter".
- No internal ticket numbers. No engineer names.
- One line per item; link the PR in parentheses.
Example
Input: feat(export): add CSV export for reports (#412)
Output: - Export any report to CSV from the Share menu. (#412)
References
- Tone guide: STYLE.md
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.

