release-health-gates
Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass.
Works with
--- name: release-health-gates description: Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass. license: MIT --- # Release Health Gates ## When NOT To Use - Measuring delivery performance (use `minister:dora-metrics`) - PR-level quality gates before merge (use `sanctum:pr-prep`) ## Purpose Standardize release approvals by expressing gates as GitHub-aware checklists. Ensure code, docs, comms, and observability items are green before deployment. ## Gate Categories 1. **Scope & Risk** – Are all blocking issues closed or deferred with owners? 2. **Quality Signals** – Are required checks, tests, and soak times satisfied? 3. **Comms & Docs** – Are docs merged and release notes posted? 4. **Operations** – Are runbooks, oncall sign-off, and rollback plans ready? ## Workflow 1. Load skill to access gate modules. 2. Attach Release Gate section to deployment PR. 3. Use tracker data to auto-fill blockers and highlight overdue tasks. 4. Update comment as gates turn green; require approvals for any waivers. ## Outputs - Release Gate markdown snippet (embed in PR/issue). - QA Handshake summary referencing GitHub Checks. - Rollout scorecard that persists in tracker data for retros. ## Exit Criteria - All release gates evaluated and documented. - Any blocking gates have waiver approvals recorded. - Deployment PR contains embedded Release Gate snippet. - Rollout scorecard saved for post-release retrospective.
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
