release-health-gates

Name: release-health-gates
Author: athola

github.com/atholaCloud & DevOps34399 installsUpdated 1d ago

About release-health-gates

A release-approval workflow that represents deployment readiness as GitHub-aware checklists covering risk, quality, communications, and operations. It is for teams coordinating release approvals, waivers, and rollout records through deployment PRs and tracker data.

Key features

01Categorized release gates
02Blocker tracking and overdue flags
03Approval records for waivers
04Deployment PR gate snippets
05Persistent rollout scorecards

Use cases

01Checking readiness before deployment
02Tracking release blockers and waivers
03Recording rollout results for retrospectives

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/athola/claude-night-market --skill release-health-gates

After installing, type/release-health-gatesin Claude Code to confirm it loaded.

Bundled filesmodules/deployment-readiness.mdmodules/quality-signals.md

Details

From the project README

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.

Comments

Markdown supported

Details

Author: athola
Repository: athola/claude-night-market
Category: Cloud & DevOps
Installs: 99
GitHub stars: 343

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.