What problem does it solve? Writing release notes by hand means digging through git history, classifying commits, and rewriting them into user-facing language. This Skill automates that workflow by delegating to a repo's own generator script when one exists, or falling back to git-range analysis with templates. ## Core Features & Use Cases - Repo generator delegation: When build/scripts/generate-release-notes.ts exists, it runs npm run release:notes with flags mapped from user intent (tag, explicit range, or since last release) instead of re-parsing git history. - Generic git-range fallback: For repos without a generator, it classifies commits by conventional-commit prefixes and formats them with github.md, slack.md, or changelog.md templates. - Use Case: After tagging v1.47.1, ask for the release notes and get a ready-to-review draft file built from the last tag range, without manually scanning git log. ## Quick Start Ask the assistant to generate release notes for the current repository since the last tag and show the draft before publishing.
