What problem does it solve? Releasing HOT-Step CPP involves a tag-triggered CI pipeline with non-obvious constraints: any pushed v* tag fires ~11 build jobs, no version files exist to bump, caches are ref-scoped, and a wrong tag silently corrupts release notes. This Skill encodes the exact runbook, golden rules, and failure signatures so releases ship correctly the first time. ## Core Features & Use Cases - Tag-driven release runbook: Step-by-step procedure for tagging vX.Y.Z, monitoring the Release workflow, verifying the 24-asset draft, and publishing with gh CLI. - Throwaway CI compile tests: Use hyphenated tags (e.g. vX.Y.Z-CI-Test) to test the full build matrix without polluting the changelog, plus cleanup commands. - Failure diagnosis: A symptom-to-fix table covering cold caches, nvcc runner mismatches, ninja mtime loops, truncated release notes, and stale-object mixed-ABI crashes. - Use Case: A maintainer asks to "cut release v1.4.0" — the Skill enforces the preconditions (clean master, check-release-prereqs.mjs passing, user approval before push), then walks through tagging, monitoring, asset verification, and draft publishing. ## Quick Start Ask the assistant to cut release vX.Y.Z of HOT-Step CPP and follow the release-process runbook to tag, monitor CI, and publish the draft.