skills.rest
nguyenpv1980-wq
nguyenpv1980-wqCOMMUNITY
Explore all skills by this author →
GitHub

merge-is-deploy-governance

Document repositories where mainline merges auto-deploy to production.

2|Updated Jul 6, 2026
Search Tags:#rollback#branch protection#pr validation#deployment governance#merge to deploy#pipeline policy
One-click install
npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill merge-is-deploy-governance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-is-deploy-governance
Source: https://github.com/nguyenpv1980-wq/Project-Aegis/tree/main/.claude/skills/merge-is-deploy-governance
Command: npx skills add https://github.com/nguyenpv1980-wq/Project-Aegis --skill merge-is-deploy-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about merge-is-deploy-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I govern deployments when merging to mainline automatically deploys to production?▼

Merge-to-deploy governance documents the real pipeline triggers, promotes PR validation as the authoritative pre-production gate, and records branch protection rules to make automatic production deployments safe and explicit.

What is the correct pre-production validation gate for a pipeline that auto-deploys on merge?▼

The PR-time required checks serve as the authoritative pre-production validation gate for auto-deploy pipelines, while post-merge smoke tests are demoted to verification only, ensuring risk is not hidden in an unstated merge window.

How do I document rollback rules that match my branch merge strategy?▼

Rollback rules must match your branch merge strategy by preserving the correct revert mechanics for squash, merge, or rebase histories, alongside the protected branch configuration and human ownership of protection changes.

Can I use this deployment governance for a Vercel or Netlify auto-deploy pipeline?▼

Yes, this governance applies to repositories on Vercel, Netlify, or GitOps hosts where mainline merges deploy immediately, capturing what merge triggers and what environments receive it to make partial auto-deploy realities explicit.

Why does my post-merge smoke test not count as a pre-production gate?▼

Post-merge smoke tests act as verification only because the deployment to production has already been triggered by the merge, meaning the PR validation checks are the true pre-production gate that prevents unsafe changes from merging.

How do I record branch protection changes for an auto-deploying mainline branch?▼

Branch protection records must preserve the protected branch configuration and require human ownership of protection changes, ensuring the exposure window acceptance and deployment triggers remain explicitly governed and auditable.

Related Skills

Explore More Software Engineering Skills→
kenkenmainkenkenmain
1

gh-repo-setup

Automate GitHub repository setup with GitFlow, branch protection, templates, and CI.

Official
Advanced
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic
app-vitalsapp-vitals
9

repo-config

Configure branch protection, required checks, secrets, and deploy hooks for merge gates.

Official
Advanced
aspectrraspectrr

land-and-deploy

Merge approved GitHub PRs, deploy to production, and verify health.

Community
Advanced