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.