merge-is-deploy-governance

What problem does it solve?

This Skill prevents teams from treating post-merge checks as if they were a pre-production gate on platforms where merging to mainline automatically deploys to production. It aligns the written governance with the actual deployment reality so the team does not hide risk in an unstated merge-to-verify window.

Core Features & Use Cases

• Document the real pipeline: Captures what merge triggers, what environment receives it, and what does not auto-deploy, such as separately applied migrations.
• Promote the correct gate: Reframes PR-time required checks as the authoritative pre-production validation and demotes post-merge smoke tests to verification only.
• Record branch protection and rollback rules: Preserves the protected branch configuration, human ownership of protection changes, exposure-window acceptance, and the correct revert mechanics for squash, merge, or rebase histories.
• Use case: A repository on Vercel, Netlify, or a GitOps host deploys every mainline merge immediately, and the team needs standing governance that makes that reality explicit and safe.

Quick Start

Ask the skill to write merge-is-deploy governance for this repository, including the verified deployment reality, PR gate, branch-protection record, exposure window, and rollback primitive.