| 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. |
| alwaysApply | false |
| category | governance |
| tags | ["release","github","readiness","quality","governance"] |
| dependencies | [] |
| tools | [] |
| provides | {"governance":["release-gates","rollout-scorecards"],"reporting":["deployment-comment","qa-handshake"]} |
| usage_patterns | ["release-train","hotfix-review","stakeholder-briefing"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 700 |
| progressive_loading | true |
| modules | ["modules/quality-signals.md","modules/deployment-readiness.md"] |
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
- Scope & Risk – Are all blocking issues closed or deferred with owners?
- Quality Signals – Are required checks, tests, and soak times satisfied?
- Comms & Docs – Are docs merged and release notes posted?
- Operations – Are runbooks, oncall sign-off, and rollback plans ready?
Workflow
- Load skill to access gate modules.
- Attach Release Gate section to deployment PR.
- Use tracker data to auto-fill blockers and highlight overdue tasks.
- 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.
