- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add silverstein/minutes --skill minutes-release-notes -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add silverstein/minutes --skill minutes-release-notes -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add silverstein/minutes --skill minutes-release-notes -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add silverstein/minutes --skill minutes-release-notes -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/silverstein/minutes/tree/HEAD/.agents/skills/minutes/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.
Collect:
v0.22.0HEADResolve missing refs from the repository instead of guessing:
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:
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.
Read two or three recent stable releases before writing:
gh release list --limit 5
gh release view <recent-tag>
Match the current heading hierarchy, amount of detail, install wording, contributor treatment, and overall tone. Prefer concrete user outcomes, honest limitations, and short technical explanations. Do not copy stale version-specific claims.
Never use em dashes in the draft. Rewrite with commas, colons, parentheses, or separate sentences. This is a repository release convention, not an optional style preference.
Read the full range and inspect touched files when a subject is unclear:
git log <previous-tag>..HEAD --pretty='%s (%h)'
git diff --stat <previous-tag>..HEAD
git show --stat <commit>
Classify every relevant commit by conventional prefix:
feat -> Featuresfix -> Fixesperf -> Performancedocs, chore, build, ci, test, and uncategorized maintenance -> Docs / Chore rollupTreat merge commits and follow-up fixes as part of the user-visible change they complete. Deduplicate stacked or backported commits. Use file inspection to verify the affected surface: desktop, CLI, MCP and agent integrations, site, plugin, SDK, or shared engine.
Drop internal-only version bumps, lockfile syncs, generated-file refreshes, formatting, test-only changes, CI churn, and release bookkeeping unless they change installation, compatibility, reliability, security, or another user-visible behavior. Do not inflate the notes with one bullet per commit.
Lead with one or two sentences that state why the release exists. Convert the strongest Features and Performance items into outcome-led headline sections. Roll smaller items into Fixes. Include Docs / Chore items only when users must act on them or will notice the result.
For each claim:
Do not infer a breaking change, migration, benchmark, security property, compatibility promise, or contributor from the subject line alone. Verify it in the diff, release procedure, or repository documentation.
Run the repository version check after the release version has been applied:
node scripts/check_version_sync.mjs --release
If the check fails because the requested version has not been bumped yet, report that clearly. Do not change versions as part of drafting notes unless the user asked for release preparation too.
Search the range for configuration, storage, schema, feature-default, platform-support, and install-path changes. State either the required migration or that no migration is required. Never leave breaking-change status implicit.
Follow the closest of the recent releases inspected in step 1. Use this current Minutes layout when those releases do not establish a more specific pattern:
## Minutes vX.Y.Z
<One short paragraph explaining why this release matters.>
### <Feature or outcome headline>
<User-facing explanation, with bullets only when they improve scanning.>
### <Additional feature or performance headline, if needed>
<User-facing explanation.>
### Fixes
- <Grouped, concrete fix>
### Notes
<Breaking change, migration, compatibility, preview, or known-issue note. Say "No migration is required" when that is the verified result.>
## Install / update
The desktop app updates itself: open Minutes and it pulls vX.Y.Z on next launch, or grab the DMG from the assets below.
- **DMG**: download from the release assets below
- **CLI**: `brew install silverstein/tap/minutes` or `cargo install minutes-cli`
- **MCP**: `npx minutes-mcp` (or update the Claude Desktop extension)
## Claude Code plugin
<Include only when the plugin changed. Use the refresh commands and wording from a recent release.>
---
<Use the current release-preparation credit and contributor block only when recent releases include them and the credits are verified.>
Keep the install block wording and order exact unless the repository's current distribution paths changed. Omit empty feature sections, but never omit the install block or breaking-change and migration status.
Before returning the draft, verify:
node scripts/check_version_sync.mjs --release passes, or its version-bump blocker is reported.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 r
---name: minutes-release-notesdescription: Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the…---# .agents/skills/minutes/minutes-release-notes/SKILL.md개요
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.
FAQ
게시자에게서 .agents/skills/minutes/minutes-release-notes/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/silverstein/minutes에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.