Skip to content
Back to skills

Release Health Gates

ASecurity

'Standardizes release approvals with GitHub-aware checklists. Use when

  • 4 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
code-qualitygoexpressgit

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill release-health-gates --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Release Health Gates?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Release Health Gates
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-release-health-gates/badge)](https://www.skillsdirectory.com/skills/micsapp-release-health-gates)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: release-health-gates
description: '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 review skills.'
category: governance
tags:
- release
- github
- readiness
- quality
- governance
dependencies: []
tools:
- minister-tracker
provides:
  governance:
  - release-gates
  - rollout-scorecards
  reporting:
  - deployment-comment
  - qa-handshake
usage_patterns:
- release-train
- hotfix-review
- stakeholder-briefing
complexity: intermediate
estimated_tokens: 700
progressive_loading: true
modules:
- modules/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

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.
## 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

Files in this skill

  • SKILL.md2.2 KB
  • modules/deployment-readiness.md920 B
  • modules/quality-signals.md860 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…