What problem does it solve? Cutting a release involves error-prone decisions: picking the right semver bump, tagging the correct commit, and writing notes that tell users whether to upgrade. This Skill guides the full release workflow so version numbers stay honest and notes stay useful. ## Core Features & Use Cases - Semver decision support: Chooses major, minor, or patch bumps based on the nature of changes, including Conventional Commits signals and pre-release labeling. - Tag and release mechanics: Reads current state via GitHub MCP tools (list_releases, get_latest_release, list_tags) and creates releases with gh release create or the REST API, with draft and pre-release handling. - Release notes authoring: Structures notes with Keep a Changelog sections, breaking-change call-outs, migration steps, and curated highlights instead of raw auto-generated lists. - Use Case: After merging a sprint of PRs, ask for the next version and a drafted release — the Skill inspects existing tags, proposes v1.5.0, and drafts grouped notes with upgrade guidance. ## Quick Start Ask the assistant to draft the next GitHub release for this repository, including the version number, tag, and release notes based on recently merged pull requests.
