What problem does it solve? Releasing Keyhac spans two operating systems, a Makefile pipeline, PyPI, the Microsoft Store, and a hand-written release note — a process where a missed artifact or a wrong version bump becomes a permanent, unpublishable mistake. This Skill walks you through every gate in order so nothing ships silently incomplete. ## Core Features & Use Cases - Version confirmation and pre-tag checks: maps patch/minor/major requests to a concrete version, confirms it with you, and runs judgment checks (git log review, generated-artifact checks, the standing interactive test pass) that the automated preflight cannot cover. - Orchestrated Makefile pipeline: runs make tag, release-github, release-macos-dmg, release-whl, and release-skill in the right order, with each target independently re-runnable. - Hand-written release notes: replaces GitHub's auto-generated PR list with a user-facing note following the project's established style. - Cross-machine completion: a dedicated Windows path attaches the portable zip and optionally submits the MSIX to the Microsoft Store against an existing tag. - Use Case: You say "release a patch version of Keyhac" — the Skill confirms 2.2.3 becomes 2.2.4, verifies the interactive test pass status, cuts the tag, publishes the Release with a proper note, and reports the Windows artifacts as remaining for the second session. ## Quick Start Tell the assistant "release a patch version of Keyhac" and it will confirm the target version with you before running the pre-tag checks and the release pipeline.
