How do I install the Ucx Github Deploy Governance skill?

Run npx skillmds add vladm3105/ucx-github-deploy-governance in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ucx Github Deploy Governance safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ucx Github Deploy Governance?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ucx Github Deploy Governance free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ucx Github Deploy Governance?

vladm3105 (@vladm3105) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ucx Github Deploy Governance by vladm3105

Name: Ucx Github Deploy Governance
Rating: 4.2 (5 reviews)
Author: vladm3105

File contents

UCX GitHub Deploy Governance Skill

Purpose

Manage deployment and QA governance loop after PR submission/merge using GitHub workflows, issue automation, and policy checks.

CI/CD Governance Scope

CI workflow status verification (required checks)
QA issue generation and tracking for functional changes
Staging readiness checks
Production readiness verification
Post-deployment outcome validation and issue closure/reopen decisions

Standard Governance Loop

PR submitted with linked issue and traceability.
Required CI checks execute.
Round-based UCX governance gates execute (up to 2 rounds).
If gates pass, merge and create/track deployment + QA issues as required.
Validate staging evidence.
Validate production readiness evidence.
Close issues on success; reopen/create bug issues on regression.

QA and Deployment Rules

Create QA issues for functional changes.
Use bounded bug-fix iterations for staging failures.
Block production progression when readiness checks fail.
Preserve evidence links in deployment and QA issues.

Observability-Driven Reopen Policy

If post-deployment monitoring shows incidents or regressions:

Open or reopen GitHub issue with severity, impact, and repro context.
Include traceability links to source artifacts and PR/deploy evidence.
Route issue back to ai:ready queue only after approval policy conditions.

GitHub Actions Compatibility Rules

Use reviewed, version-pinned workflow actions.
Respect branch protection and required checks.
Treat AI review as gate signal, not required human reviewer substitute.

UCX V3 Boundaries

Deployment governance does not bypass UCX document lifecycle gates.
CLI usage allowed for approved IPLAN implementation execution tasks only.
Lifecycle source of truth remains UCX MCP stage outputs and governance policies.

Initialization and plan-approval dependency:

Deployment/QA progression assumes issue work entered implementation only after required initialization (sdd_init/sdd_preflight when needed), planning review, gap fixing, and plan approval.

Failure Handling

If deployment governance checks fail:

Hold progression to next environment.
Record failed checks and evidence paths.
Open/update corrective issue and assign next governance action.

---name: ucx-github-deploy-governancedescription: Hermes governance skill for CI/CD, QA, staging/production readiness, and post-deployment issue-loop control aligned with governance policies.--- # UCX GitHub Deploy Governance Skill ## Purpose Manage deployment and QA governance loop after PR submission/merge using GitHub workflows, issue automation, and policy checks. ## CI/CD Governance Scope - CI workflow status verification (required checks) - QA issue generation and tracking for functional changes - Staging readiness checks - Production readiness verification - Post-deployment outcome validation and issue closure/reopen decisions ## Standard Governance Loop 1. PR submitted with linked issue and traceability. 2. Required CI checks execute. 3. Round-based UCX governance gates execute (up to 2 rounds). 4. If gates pass, merge and create/track deployment + QA issues as required. 5. Validate staging evidence. 6. Validate production readiness evidence. 7. Close issues on success; reopen/create bug issues on regression. ## QA and Deployment Rules - Create QA issues for functional changes. - Use bounded bug-fix iterations for staging failures. - Block production progression when readiness checks fail. - Preserve evidence links in deployment and QA issues. ## Observability-Driven Reopen Policy If post-deployment monitoring shows incidents or regressions: 1. Open or reopen GitHub issue with severity, impact, and repro context. 2. Include traceability links to source artifacts and PR/deploy evidence. 3. Route issue back to `ai:ready` queue only after approval policy conditions. ## GitHub Actions Compatibility Rules - Use reviewed, version-pinned workflow actions. - Respect branch protection and required checks. - Treat AI review as gate signal, not required human reviewer substitute. ## UCX V3 Boundaries - Deployment governance does not bypass UCX document lifecycle gates. - CLI usage allowed for approved IPLAN implementation execution tasks only. - Lifecycle source of truth remains UCX MCP stage outputs and governance policies. Initialization and plan-approval dependency: - Deployment/QA progression assumes issue work entered implementation only after required initialization (`sdd_init`/`sdd_preflight` when needed), planning review, gap fixing, and plan approval. ## Failure Handling If deployment governance checks fail: 1. Hold progression to next environment. 2. Record failed checks and evidence paths. 3. Open/update corrective issue and assign next governance action.

Frequently asked questions