release-health-gates
// Standardizes release approvals with GitHub-aware checklists. Use when preparing releases, validating deployment gates, conducting release reviews, embedding release gate snippets in PRs. Do not use when weekly status updates - use github-initiative-pulse. DO NOT use when: code reviews - use pensive
$ git log --oneline --stat
stars:201
forks:38
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namerelease-health-gates
descriptionStandardize release approvals with GitHub-aware checklists and deployment gate validation.
alwaysApplyfalse
categorygovernance
tagsrelease,github,readiness,quality,governance
dependencies
tools
provides[object Object]
usage_patternsrelease-train,hotfix-review,stakeholder-briefing
complexityintermediate
model_hintstandard
estimated_tokens700
progressive_loadingtrue
modulesmodules/quality-signals.md,modules/deployment-readiness.md
Release Health Gates
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.