Skill

release-health-gates

Standardizes release approvals using GitHub checklists for gates on scope, quality signals, docs, comms, and operations readiness before deployment.

GitHub

Git

git-workflow

deployment

npx claudepluginhub athola/claude-night-market --plugin minister

Popularity

Parent stars

279

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/minister:release-health-gates

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Standardize release approvals by expressing gates as GitHub-aware checklists. Ensure code, docs, comms, and observability items are green before deployment.

Supporting Files

modules/deployment-readiness.mdmodules/quality-signals.md

SKILL.md

79 lines · ~521 tokens

Similar Skills

Creating Quality Gates

Creates structured quality gates for workflow boundaries like pre-merge checklists, deployments, and phase transitions with pass/fail criteria, exact commands, and escalation procedures.

cipherpowers

deploy-checklist

12.3k

Generates customizable pre-deployment checklists to verify CI status, tests, reviews, migrations, feature flags, rollback plans, and monitor production deploys.

engineering

deploy-checklist

Generates pre-deployment verification checklists customized to the project's tech stack, including rollback triggers and graph-based module boundary validation.

draft

Stats

LanguagePython

Parent stars279

Parent forks23

MaintenanceExcellent

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

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.

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag