Release notes

Skill shinzoxD/knackbox/skills/documents/release-notes

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill release-notes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 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 author says it does

Copied from the file, not written here

Write clear user-facing and developer release notes from commits, PRs, and changelogs. Use whenever the user asks for release notes, a changelog entry, what's new for a version, ship notes for customers or engineers, or a summary of changes between tags — even if they only paste commit subjects or merged PR titles.

The file declares its own license as Apache-2.0. 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

3.4 KB, as published. Nobody here has run it

Release Notes

Turn a pile of commits into notes people actually read. Audience decides vocabulary; honesty decides what ships in the list.

Choose the audience

Audience	Voice	Include	Exclude
Users / customers	benefits, plain language	new capabilities, fixes they feel, migration steps they must take	refactors, dependency bumps, internal renames
Developers / operators	precise, technical	API changes, config flags, deprecations, upgrade steps	marketing fluff
Mixed / CHANGELOG.md	Keep a Changelog style	Added / Changed / Fixed / Deprecated / Removed / Security	empty sections

If the user does not specify, default to mixed Keep a Changelog and offer a short user-facing blurb on top when the release is product-visible.

Workflow

Cluster commits/PRs by user-visible theme (not by file or author).
Drop noise: "fix typo", "merge main", pure formatting, WIP reverts that cancel out — unless security-relevant.
Rewrite each item as an outcome: what changed for the reader, not "updated FooService".
Call out breaking changes and security fixes first, with upgrade steps.
Attach version, date (ISO), and compare link placeholders if unknown.

Output formats

Keep a Changelog (default)

## [X.Y.Z] — YYYY-MM-DD

### Security
- …

### Breaking changes
- … Migration: …

### Added
- …

### Changed
- …

### Fixed
- …

### Deprecated
- …

### Removed
- …

Omit empty sections.

Customer "What's new"

# What's new in <Product> X.Y

**Highlights**
- One sentence each, benefit-led.

**Improvements**
- …

**Fixes**
- …

**Action required** (only if any)
- What to do, by when, link/placeholder for docs.

Rules

Never invent features. If the commit list is ambiguous, write the safest reading and mark uncertainty with [confirm: …].
One bullet = one idea. Merge five "fix null checks" commits into one "Fixed crashes when …" when the user-visible effect is the same.
Prefer user language: "Export to CSV" not "Added ExportService#toCsv".
Security fixes get a clear description of the impact class without a usable exploit recipe.
Breaking changes must include a migration path or an explicit "no automatic migration".
Keep the whole notes set scannable: ~5–15 bullets for a normal release; summarize long tails under "Other fixes".

Edge cases

Only conventional commit subjects: group by type (feat→Added, fix→Fixed, feat!/BREAKING→Breaking) then rewrite titles in prose.
Hotfix / patch: lead with the fix and who should upgrade; skip empty marketing sections.
Internal platform release: developer audience by default; include config and observability changes.
Nothing user-visible: say so, produce a short internal changelog, and do not fake "Highlights".