What problem does it solve? Deploying to production without a documented release plan leads to unreviewed migrations, missing rollback paths, and unclear ownership when something breaks. This Skill produces a structured release dossier (.release-approval.json) that a PreToolUse release-gate hook requires before allowing commands like vercel --prod or supabase db push. ## Core Features & Use Cases - Release dossier generation: Captures the exact HEAD SHA, changelog, risk assessment, blast radius, and CI status for the commit being exposed. - Migration and exposure control: Classifies data migrations as none, additive, or destructive, and records feature flags or canary strategies. - Rollback and accountability: Requires a concrete rollback plan, smoke test list, observability target, and an on-call owner before the gate will pass. - Use Case: Before running a production deploy, invoke the skill to walk through the eight-step checklist, get QA/security/release sign-off on the current SHA, and write the approval file the release-gate hook validates. ## Quick Start Ask the assistant to run the release skill to prepare the deployment dossier for the current commit before pushing to production.
