Release Health Gates
- 91 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Release Health Gates is an agent skill that enforces deployment readiness and quality-signal checklists with GitHub-comment evidence before and after release.
About
Release Health Gates is an agent skill that packages two coordinated checklists—Deployment Readiness and Quality Signals—for indie builders shipping through GitHub-backed release trains. It tells your agent to mirror readiness criteria in the deployment PR, export tracker CSV to confirm no open High-priority in-scope work, attach an executive status-report excerpt, and capture sign-offs as PR approvals with explicit handles. The quality gate insists on sustained green checks, rerun integration tests after the last commit, flaky-test tracking issues, performance benchmarks on the PR, and SRE error-budget review. Included GitHub API references help you snapshot check suites and deployment status instead of hand-waving QA. After deploy, it prompts tracker closure, a retro tied to the Release Gate comment, and artifact archival. Use when you are one person playing PM, release manager, and on-call and need a repeatable comment template auditors and future-you can trust.
- Deployment Readiness Gate with required inputs: filled deployment template, rollback in PR, validated dashboards, suppor
- GitHub comment skeleton for release readiness with scope freeze, QA, docs, support brief, and rollback owner
- Quality Signals Gate checklist covering 24h green checks, integration reruns, flaky triage, benchmarks, and error budget
- Data-source table mapping checks, deployments, and issues to GitHub REST endpoints for evidence snapshots
- Post-deployment steps: mark tracker Done, retro discussion, archive artifacts under release-train-health references
Release Health Gates by the numbers
- 91 all-time installs (skills.sh)
- Ranked #115 of 248 Release Management skills by installs in the Skillselion catalog
- Security screen: HIGH risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill release-health-gatesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 91 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 2 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Run deployment readiness and quality-signal gates so a developer’s release PR has rollback, observability, checks, and sign-offs documented before prod.
Who is it for?
Best when you use GitHub PRs, trackers, and staging/prod deployments and want release train discipline without a full release manager.
Skip if: Pure local CLI drops with no GitHub checks, deployments, or shared tracker—most steps assume a repo-centric release process.
When should I use this skill?
Use when preparing a named production release and you need PR-visible readiness and quality evidence gates.
What you get
Your deployment PR carries mirrored gates, linked evidence, executive summary excerpt, and recorded sign-offs—then post-deploy tracker and retro steps are logged.
- Release Readiness GitHub PR comment
- Quality Signals evidence snapshot notes
- Post-deploy tracker updates and retro link
By the numbers
- 5-item Quality Signals Gate checklist
- 4-row GitHub data-sources table for checks and deployments
Files
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.
Deployment Readiness Gate
Required Inputs
- Deployment issue template filled out.
- Rollback steps included in PR description.
- Observability dashboard links validated.
- Support announcement drafted.
GitHub Comment Skeleton
### Release <name> Readiness
- Scope freeze: <yes/no> (issue links)
- QA status: <check summary>
- Docs merged: <PR link>
- Support brief: <discussion link>
- Rollback owner: @handleSteps
1. Mirror this checklist in the deployment PR. 2. Use tracker CSV export to confirm no open High priority work in release scope. 3. Attach status-report-template.md excerpt for executive summary. 4. Capture final sign-offs as PR approvals and mention handles.
Post-Deployment
- Update tracker tasks to
Doneand log actual effort. - Create retro discussion referencing Release Gate comment.
- Archive artifacts under
docs/playbooks/release-train-health.mdreferences.
Quality Signals Gate
Checklist
- [ ] Required GitHub checks green for 24h.
- [ ] Integration tests rerun after last commit.
- [ ] Flaky tests triaged with tracking issue link.
- [ ] Performance benchmarks attached to PR comment.
- [ ] Error budget impact reviewed with SRE.
Data Sources
| Signal | GitHub Source | Notes |
|---|---|---|
| Checks | GET /repos/{owner}/{repo}/commits/{sha}/check-suites | Store snapshot hash in tracker notes. |
| Deployments | GET /repos/{owner}/{repo}/deployments | Validate staging and prod status. |
| Issues | label:qa-blocker | Drive gating conversation. |
Escalation Path
1. If any check fails, tag @release-captain and owning engineer in PR. 2. Log blocker in tracker with status="In Progress" and pointer to GitHub artifact. 3. Update Release Gate comment with mitigation ETA.
Related skills
Changelog AutomationAutomatically generate accurate, well-structured changelogs from commit history and Conventional Commits.11.2k38.5k
Msstore CliAutomate publishing, managing submissions, and handling CI/CD for Windows apps in the Microsoft Store.7k37.5k
Changelog GeneratorAutomatically turn git commit history into polished, customer-friendly release notes without manual rewriting.5.9k71.8k
Deploy ChecklistGenerate a complete pre-deployment verification checklist tailored to their service or release.4.6k23.3k
Opensource PipelineSafely strip secrets, sanitize code, and generate required open-source files before releasing a private project publicly.4.3k238k
Community PublishInstantly share running services with public URLs, list projects on a discoverable dashboard, or open-source code to a community GitHub repository.3.9k21How it compares
Structured release gate checklists in the agent, not a CI platform replacement or automatic deploy button.
FAQ
Who is release-health-gates for?
Developers and tiny teams shipping named releases who need PR-comment readiness and quality evidence without hiring a release manager.
When should I use release-health-gates?
In Ship launch before promoting to production; in Ship review when freezing scope; and in Operate iterate when closing a release with retro and artifact archival.
Is release-health-gates safe to install?
It guides documentation and GitHub API reads for evidence; review the Security Audits panel on this page and scope any tokens to least privilege.