release-it

Diagnose and harden production systems using stability patterns, capacity planning, and chaos engineering.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill release-it-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-it
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/release-it
Command: npx skills add https://github.com/HafidJoss/Lummy --skill release-it-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Production systems fail in ways that testing never reveals: cascading failures, retry storms, pool exhaustion, and botched deployments. This Skill provides a structured framework based on Michael Nygard's Release It! to audit, score, and harden systems against real-world failure modes before they cause outages. ## Core Features & Use Cases - Stability Audit & Scoring: Run an 8-point Quick Diagnostic covering timeouts, circuit breakers, bulkheads, zero-downtime deploys, deep health checks, correlated telemetry, load testing, and failure injection, with a scored assessment and specific fixes per failing row. - Stability Pattern Implementation: Apply circuit breakers, bulkheads, timeouts, retry budgets with backoff and jitter, and fail-fast behavior to stop cascading failures at integration points. - Capacity & Deployment Planning: Design load, stress, soak, and spike tests, size connection and thread pools from measured concurrency, and plan blue-green, canary, or rolling deployments with expand-contract database migrations. - Use Case: Your service keeps crashing under load. Use this Skill to audit every integration point, identify which stability anti-patterns are present (e.g., missing read timeouts, shared thread pools), and get a concrete remediation plan with tuned circuit breaker thresholds and isolated resource pools. ## Quick Start Ask the assistant to audit your production service using the Release It! quick diagnostic and list which stability patterns are missing.

Frequently Asked Questions about release-it

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

FAQPage Schema
How do I prevent cascading failures between microservices?

Prevent cascading failures by combining circuit breakers, timeouts, and bulkheads at every integration point. Circuit breakers stop calls to failing dependencies, timeouts free blocked threads, and bulkheads isolate resource pools so one failing dependency cannot drain the whole system.

How do I implement a circuit breaker for service calls?

Implement a circuit breaker with three states: closed, open, and half-open. Trip it after a threshold such as 5 failures in 60 seconds, then test recovery with limited traffic after 30 seconds. Combine it with connect and read timeouts on every outbound call.

What is the difference between blue-green and canary deployment?

Blue-green deployment switches all traffic between two full environments, giving instant rollback but requiring double infrastructure. Canary releases route a small traffic percentage to the new version with automated metric evaluation, minimizing risk exposure at lower infrastructure cost.

How do I size database connection pools correctly?

Size connection pools from measured concurrency, not defaults: set the pool to p99 active connections plus 20-30% headroom. Always configure checkout timeouts, maximum connection lifetime, and leave headroom below the database's own connection limit for admin access.

When should I not run chaos engineering experiments in production?

Avoid production chaos experiments during peak traffic, without an emergency stop mechanism, or before validating the experiment in staging. Start with minimal blast radius such as a single instance or canary population, and require explicit authorization with rollback plans.