minutes-release-notes
Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks. Use when the user asks to write, generate, prepare, revise, or review release notes or a changelog for a Minutes version.
npx skills add silverstein/minutes --skill minutes-release-notes --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# /minutes-release-notes Draft release notes that explain why a Minutes release matters without making users decode the commit history. Produce a draft only. Do not create, edit, or publish a GitHub release unless the user explicitly asks. ## Inputs Collect: - the new version, such as `v0.22.0` - the previous stable tag, or an explicit starting ref - the target ref, normally `HEAD` - the release channel, normally stable or preview - any known breaking changes, migrations, compatibility notes, or contributor credits Resolve missing refs from the repository instead of guessing: ```bash git describe --tags --abbrev=0 git log <previous-tag>..HEAD --pretty='%s (%h)' ``` When `HEAD` is already tagged, resolve the previous tag from its parent so the range does not collapse to zero commits: ```bash git describe --tags --abbrev=0 HEAD^ ``` Confirm both refs with `git rev-parse --verify` before drafting. If the version or range is ambiguous, ask one short question. ## Steps ### 1. Learn the current release voice Read two or three recent stable releases before writing: ```bash gh release list --limit 5 gh release view <recent-tag> ``` Match the current heading hierarchy, amount of detail, ins
- Inputs
- Steps
- 1. Learn the current release voice
- 2. Build the change ledger
- 3. Turn the ledger into release prose
- 4. Check release integrity
- Output format
- Checklist
git describe --tags --abbrev=0 git log <previous-tag>..HEAD --pretty='%s (%h)' git describe --tags --abbrev=0 HEAD^ gh release list --limit 5 gh release view <recent-tag> git diff --stat <previous-tag>..HEAD git show --stat <commit> node scripts/check_version_sync.mjs --release
What does the minutes-release-notes skill do?
Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks. Use when the user asks to write, generate, prepare, revise, or review release notes or a changelog for a Minutes version.
How do I install it?
Run `npx skills add silverstein/minutes --skill minutes-release-notes --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.