minutes-release-notes

Draft user-facing release notes for Minutes versions from git commit ranges and GitHub releases.

1.5k|158|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/silverstein/minutes --skill minutes-release-notes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minutes-release-notes
Source: https://github.com/silverstein/minutes/tree/main/tooling/skills/sources/minutes-release-notes
Command: npx skills add https://github.com/silverstein/minutes --skill minutes-release-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing accurate release notes requires reading an entire commit range, classifying changes, matching the project's established voice, and verifying version integrity, which is tedious and error-prone when done manually.

Core Features & Use Cases

  • Commit Range Analysis: Resolves the previous tag and target ref with git commands, then classifies every commit by conventional prefix (feat, fix, perf, docs, chore) into a change ledger.
  • Voice Matching: Reads two or three recent GitHub releases to match heading hierarchy, tone, install wording, and contributor treatment, enforcing repository conventions like the no-em-dash rule.
  • Release Integrity Checks: Runs the repository version sync check and explicitly states breaking changes, migrations, and compatibility notes.
  • Use Case: A maintainer preparing Minutes v0.22.0 asks for release notes and receives a polished draft with feature headlines, grouped fixes, the standard DMG/CLI/MCP install block, and a verified migration statement.

Quick Start

Ask the assistant to draft release notes for Minutes v0.22.0 using the commit range since the previous stable tag.

Frequently Asked Questions about minutes-release-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from a git commit range?

Resolve the previous tag with git describe --tags --abbrev=0, list commits with git log <previous-tag>..HEAD, then classify each commit by conventional prefix into Features, Fixes, Performance, and Docs/Chore sections before writing prose.

How to write release notes that match a project's existing style?

Read two or three recent releases with gh release list and gh release view, then match their heading hierarchy, detail level, install wording, and tone. Avoid copying stale version-specific claims from older releases.

Does this skill publish GitHub releases automatically?

No, it produces a draft only. It does not create, edit, or publish a GitHub release unless the user explicitly asks, and it does not bump versions unless release preparation was requested.

What commits should be excluded from release notes?

Drop internal-only version bumps, lockfile syncs, generated-file refreshes, formatting, test-only changes, and CI churn unless they affect installation, compatibility, reliability, security, or other user-visible behavior.

Why does the version check fail when drafting release notes?

The node scripts/check_version_sync.mjs --release check fails when the requested version has not been bumped in the repository yet. Report this blocker clearly rather than changing versions during note drafting.