release-notes
/release-notes
Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal.
- Author
- VladButacu ↗
- Repository
- agentkit ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal.
Original author description
Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal.
How it works
- Discover the convention first
- Source of truth
- Voice
- Shape
- Translate
SKILL.md preview
--- name: release-notes description: Use when a changelog entry must become user-facing release notes for a release. Skip changelogs that stay internal. disable-model-invocation: false metadata: opencode/autoinvoke: true --- # 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.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · VladButacu/agentkit | 85 | MIT |
| mono/SkiaSharp | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| kenryu42/cc-safety-net | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| openshift-pipelines/pipelines-as-code | 100 | Apache-2.0 |
| paperwingio/paperwing | 100 | Apache-2.0 |
| jelvodev/yaap | 100 | MIT |
| yearzen1/LocalSkillManager | 100 | MIT |
Database snapshot: 13.11.2026 · package version 76b07a6dc257 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100create-release-notes
Generate user-facing release notes when the user asks to write release notes, document a release, summarize changes for users, or prepare a changelog between versions - 90changelog-writer
Read the git log and write a user-facing changelog entry in Keep a Changelog format. Use when the user wants to document what changed in a release, write release notes, or update their CHANGELOG.md. - 100trove-release-notes
Release notes generator. Creates user-facing release notes from git history, PR descriptions, and changelog entries. Use when: release notes; draft a changelog; what shipped; update changelog. - 100write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to… - 90change-write
Write a changelog entry or release notes for an API version — breaking changes, new features, fixes. Use when asked to "write release notes", "add a changelog entry", or "document breaking changes". - 100write-changelog-entry
Use when asked to add, revise, or review a changelog or release-notes entry in this repo. Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section without overstating docs, tests,…