What problem does it solve? Cutting a GitHub Release for the PolyKybd projects involves error-prone details: resolving the correct version range from bump commits, writing customer-facing release notes in the right voice, staging notes on the release-notes branch, and avoiding traps like the [skip ci] tag-push that never triggers CI. This Skill walks through the whole process with a mandatory user review gate before anything is published. ## Core Features & Use Cases - Version range resolution: Anchors the release range on the last published GitHub release rather than in-tree bump commits, with shallow-clone detection to avoid wrong commit sets. - Release-note drafting: Applies a three-tier format (customer-facing sections, collapsed minor entries, a single maintenance line) with concise bullets and a compatibility lead-in. - Metadata and hand-off: Crafts the release title, tag, and latest flag, stages <TAG>.md on the release-notes branch, and hands the user a publish_release.py one-liner since the environment cannot push tags or publish releases. - Use Case: Ask to "release the firmware" and the Skill resolves the range (e.g. 0.9.24 to 0.9.42), drafts notes newest-first, presents them rendered for approval, then stages the file and gives you the publish command. ## Quick Start Ask the assistant to cut a GitHub release for the PolyKybd firmware, host app, or WinCompose at a specific version.
