Individual skill
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.
tooling/skills/goldens/opencode/minutes-release-notes/SKILL.md
Source commit 2e64cd4932851644b3f0829ecfa07d8052fda897
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,595
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- meetings Repository topic
- ai Repository topic
- claude Repository topic
- mcp Repository topic
- meeting-notes Repository topic
- privacy Repository topic
- rust Repository topic
- speech-to-text Repository topic
- transcription Repository topic
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# /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
