What problem does it solve? Shipping to production involves many error-prone manual steps: deciding the version, writing release notes, updating the changelog, tagging, and publishing a GitHub Release. This Skill automates the entire preprod-to-main release flow while forcing an explicit review of everything being shipped, so no one accidentally releases a colleague's unfinished work. ## Core Features & Use Cases - Blast-radius reporting: Before anything ships, it lists every commit and pull request queued on preprod, split into your own work versus work riding along from others. - Authority gating: A release only proceeds with an explicit grant in .harness-version or a direct user request in the current turn; flags like --ship alone are not sufficient. - Automated release mechanics: Computes the next semantic version, generates release notes and changelog entries, pushes a release commit to preprod via the GitHub MCP server, and lets the release.yml workflow merge to main, tag the version, and publish the GitHub Release. - Use Case: After merging several features into preprod during a sprint, run /release minor to review everything queued, confirm the scope, and ship a tagged v1.3.0 release to production in one command. ## Quick Start Run /release with an optional major, minor, or patch argument to review what is queued on preprod and ship it to production as a tagged GitHub Release.