What problem does it solve? Teams shipping to production from a GitHub repository often lack explicit rules for how rollouts actually work: when a merge does or does not deploy, how images are tagged, how migrations are verified, and how failures are detected. This Skill encodes those delivery rules so an AI assistant applies them consistently whenever an edit goes to production. ## Core Features & Use Cases - Rollout governance: Defines how merges, manual workflow_dispatch runs, image sha tagging, and rollback depth (last three shas) are handled in a GitHub Actions pipeline. - Migration safety: Requires running the migration chain from an empty storage before merge and measuring schema drift on a shadow database rather than the developer's working one. - Divergence auditing: Detects when production lags the main branch via a work queue audit that reads the last successful rollout, catching failed or never-started deployments. - Use Case: Before merging a PR that changes the deploy workflow or database schema, load this rule so the assistant enforces pre-merge pipeline runs, shadow-storage migration checks, and sha-based image rollout instead of the 'latest' tag. ## Quick Start Load the deploy-flow rule and review my pull request that changes the deploy workflow and adds a database migration before I merge it into main.