mcpbeat

Release Health Gates

athola/release-health-gates

Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass.

944 tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
324
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/athola/claude-night-market --skill release-health-gates

The instruction itself

7 sections, as written by the author

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.

How to use it

Copy the folder

Take athola/release-health-gates from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.