skills.rest
hatch3r
hatch3rOFFICIAL
Explore all skills by this author →
GitHub

hatch3r-reliability-verify

Verify production release readiness across nine reliability gates.

26|4|Updated Feb 27, 2026
Search Tags:#kubernetes#observability#reliability#progressive delivery#feature flags#runbooks#slo
One-click install
npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-reliability-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hatch3r-reliability-verify
Source: https://github.com/hatch3r/hatch3r/tree/main/skills/hatch3r-reliability-verify
Command: npx skills add https://github.com/hatch3r/hatch3r --skill hatch3r-reliability-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents agent-produced services from being marked “done” without production-grade reliability controls, so failures surface in time and rollouts don’t silently harm users.

Core Features & Use Cases

  • Reliability gate with 9 machine-checkable “done” criteria: validates SLO presence, kill switch, outbound timeouts, retries with decorrelated jitter, health probes, graceful shutdown, runbook URLs, staged rollout configuration, and blast-radius documentation.
  • Operational readiness for production: ensures alerts link to runbooks with required sections and that progressive delivery is configured to roll back on SLO burn-rate.
  • Release-prep artifact for downstream use: writes a PR verdict plus a JSON audit output for release workflow automation.
  • Use case: Before shipping a new microservice, verify that the repo’s SLO/alerts, Kubernetes probes, rollout strategy, and runbooks are complete so on-call can triage quickly and rollback confidently.

Quick Start

Run the reliability verification gate by invoking it on a PR that touches service code or Kubernetes/alert configuration, so it evaluates all nine production-readiness gates and blocks the merge on any failure.

Frequently Asked Questions about hatch3r-reliability-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Kubernetes production readiness before merging a service release?▼

Verify production readiness by checking SLO burn-rate alerts, OpenFeature kill switches, health probes, graceful shutdown, runbook URLs, and staged rollout configurations. This reliability gate blocks merges on any missing safety criteria.

What reliability checks should a microservice pass before shipping to production?▼

A microservice should pass reliability checks for SLO presence, outbound timeouts, decorrelated-jitter retries, Kubernetes liveness probes, runbook annotations, and blast-radius documentation to ensure safe progressive delivery.

How do I automate SLO and runbook verification in a Kubernetes pull request?▼

Automate SLO and runbook verification by applying a reliability gate to PRs that validates runbook_url annotations and required sections, then outputs a JSON audit and PR verdict to block incomplete merges.

Does progressive delivery require a feature flag kill switch with a runbook?▼

Progressive delivery requires an OpenFeature kill switch with runbook flip steps to ensure safe rollback. The reliability gate verifies this kill switch presence before allowing a production rollout.

What is a reliability verification gate for production releases?▼

A reliability verification gate is an automated check that enforces nine production-readiness criteria, including SLO alerts and graceful shutdown, preventing agent-produced services from being marked done without operational controls.

Can I use this gate to validate canary rollout and blast-radius documentation?▼

Yes, you can validate canary rollout configurations and blast-radius documentation. The gate requires staged rollout steps with rollback drill evidence and blocks merges if blast-radius documentation is missing.

Related Skills

Explore More Software Engineering Skills→
patricio0312revpatricio0312rev
5

alerting-dashboard-builder

Automate SLO-based alert rules and operational dashboards for service health monitoring.

Community
Advanced
sajalsuhanesajalsuhane

land-and-deploy

Merge pull requests, wait for CI, and deploy with canary validation.

Community
Advanced
robotijnrobotijn
3

feature-flag-auditor

Audit codebases for stale, orphaned, and misconfigured feature flags.

Community
Advanced
nopperabbonopperabbo
7

helm-validator

Validate Helm chart structure, lint templates, render manifests, and check YAML and CRDs.

Community
Advanced