release-health-gates
npx machina-cli add skill athola/claude-night-market/release-health-gates --openclawRelease 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
Source
git clone https://github.com/athola/claude-night-market/blob/master/plugins/minister/skills/release-health-gates/SKILL.mdView on GitHub Overview
Release Health Gates standardizes release approvals by expressing gates as GitHub-aware checklists. It ensures code, docs, comms, and observability items are green before deployment, and embeds a gate snippet in each PR for visibility. It leverages tracker data to surface blockers and supports rollouts with a persisted scorecard.
How This Skill Works
Load the skill to access gate modules, attach a Release Gate section to the deployment PR, and use tracker data to auto-fill blockers and highlight overdue tasks. As gates turn green, update the PR comment and require approvals for any waivers. Outputs include a release gate markdown snippet, QA Handshake referencing GitHub Checks, and a rollout scorecard stored in tracker data.
When to Use It
- Preparing a release for deployment
- Validating deployment gates before PR merge
- Conducting a release review with stakeholders
- Embedding Release Gate snippets in PRs or issues
- Capturing rollout scorecard for post-release retrospective
Quick Start
- Step 1: Load the skill to access gate modules
- Step 2: Attach Release Gate section to the deployment PR and embed the gate snippet
- Step 3: Use tracker data to auto-fill blockers, monitor gates, and record waiver approvals as needed
Best Practices
- Attach the Release Gate section to every deployment PR
- Rely on tracker data to auto-fill blockers and surface overdue tasks
- Seek approvals for any waiver decisions and document reasons
- Verify all gate categories (Scope & Risk, Quality Signals, Comms & Docs, Operations) are green
- Include and maintain the embedable Release Gate snippet in PRs and link to the rollout scorecard
Example Use Cases
- A hotfix deployment uses gates to validate blockers and rollback plan before merging
- A feature release ensures release notes are posted and docs are updated
- The deployment PR includes an embedded Release Gate snippet for visibility
- QA Handshake references are automatically linked to GitHub Checks
- Rollout scorecard is persisted in tracker data for post-release retrospective
