What problem does it solve? Coordinating software releases across canary and main branches involves strict PR title formats, CI trigger rules, and error-prone changelog writing where hallucinated PR numbers and wrong compare bases are common failure modes. This Skill routes each release type to the correct procedure and enforces git-derived facts for release notes. ## Core Features & Use Cases - Release Routing: Directs minor releases, weekly patch releases, hotfixes, model launches, and DB migrations to the correct step-by-step reference workflow. - CI Trigger Rules: Documents exactly which PR title prefixes and branch names trigger the auto-tag-release workflow, and which do not. - Verified Release Notes: Enforces hard rules requiring every PR reference, metric, and contributor handle to be computed from git and gh commands, with a mandatory pre-publish verification diff. - Use Case: When asked to ship the weekly release, the agent branches from canary, computes the previous semver tag from main, derives all PR refs from commit subjects, writes the changelog per the style guide, and creates the PR with the correct title format. ## Quick Start Ask the agent to prepare a weekly patch release from canary to main with verified release notes.
