convez.ai
SkillDevOps & InfraestruturaAvançado
costrict-plugins-repo

Chaos Engineering

costrict-plugins-repo/alirezarezvani-claude-code-skills-chaos-engineering

Discipline end-to-end para chaos experiments sem transformar em outage

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill Python completo para design, execução e análise de experimentos de caos em produção. Inclui ferramentas para desenhar hipóteses, calcular raio de explosão e gerar postmortems, com 7 tipos de ataque (latência, erro, recurso, partição, dependência, tempo, infraestrutura) e comando interativo para orquestração segura.

Instalação

$npx convez-ai costrict-plugins-repo/alirezarezvani-claude-code-skills-chaos-engineering

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
37%
Último commit
há 2 semanas
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Validar resiliência de serviços antes de falhas reais
  • Calcular impacto máximo de experimentos de caos (blast radius)
  • Automatizar testes contínuos de comportamento sob falhas

Veredito

Skill maduro e bem estruturado para times que querem chaos engineering disciplinado em produção. Exige expertise em SRE/DevOps, mas elimina adivinhação em design de experimentos e garante guardrails rigorosos (abort criteria, blast radius ≤10% error budget).

README

A tradução para o português deste README ainda está na fila.

Chaos Engineering

End-to-end discipline for chaos experiments — design, run, learn — without becoming an outage.

What's inside

  • 3 stdlib Python tools — experiment designer, blast-radius calculator, postmortem generator
  • 4 reference docs — principles, experiment design, attack taxonomy, tooling landscape
  • 2 templates — experiment plan, postmortem
  • /chaos-experiment slash command — interactive design wizard

Install

# Via Claude Code marketplace
/plugin install chaos-engineering

# Or clone the repo
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills/engineering/chaos-engineering

Quick start

SKILL=engineering/chaos-engineering/skills/chaos-engineering

# 1. Design an experiment
python "$SKILL/scripts/experiment_designer.py" \
  --target checkout-svc \
  --hypothesis "p99 < 500ms when payment slows" \
  --attack latency --magnitude "+200ms" \
  --abort-if "p99 > 1000ms OR error_rate > +1pp"

# 2. Calculate blast radius
python "$SKILL/scripts/blast_radius_calculator.py" \
  --traffic-share 0.05 --user-pop 1000000 \
  --duration-min 15

# 3. Generate postmortem after running
python "$SKILL/scripts/experiment_postmortem.py" \
  --plan plan.json --result-log results.txt

Key principles

  1. Build a hypothesis around steady-state behavior — measurable, falsifiable
  2. Vary real-world events — realistic failures only, not astronomy-grade
  3. Run experiments in production — staging never has prod failure modes
  4. Automate experiments to run continuously — single experiment = press release; continuous = engineering
  5. Define abort criteria up front — chaos without abort = outage

The 7 attack types

AttackTestsMagnitude examples
LatencyTimeouts, retries, circuit breakers+200ms, +2s
ErrorError handling, fallback paths1%, 50%, 100%
ResourceSaturation, autoscaling, OOM80% CPU, 90% memory, fill /var
Network partitionConsensus, leader election, failoverdrop 100% to peer X
Dependency failureGraceful degradationtimeout 100% to dep X
Time skewClocks, TTLs, retry backoff+5min, +1day
InfrastructureAuto-recovery, replica maintenancekill 1 of N

Composition with other skills

SkillComposition
feature-flags-architectKill switches there are abort triggers here
kubernetes-operatorOperators are common chaos targets
incident-responseChaos that escalates becomes an incident

Skill structure

chaos-engineering/
├── README.md
├── .claude-plugin/plugin.json
└── skills/chaos-engineering/
    ├── SKILL.md
    ├── scripts/
    │   ├── experiment_designer.py
    │   ├── blast_radius_calculator.py
    │   └── experiment_postmortem.py
    ├── references/
    │   ├── chaos_principles.md
    │   ├── experiment_design.md
    │   ├── attack_taxonomy.md
    │   └── tooling_landscape.md
    └── assets/
        ├── experiment_template.md
        └── postmortem_template.md

Verifiable success

A team using this skill should achieve:

  • 100% of chaos experiments have written hypothesis, abort criteria, blast-radius calc
  • Blast radius for any single experiment ≤10% of monthly error budget
  • Mean time between chaos experiments <14 days (continuous, not one-off)
  • Each experiment produces ≥1 follow-up action that gets shipped
  • No chaos experiment escalates to a customer-impacting incident in trailing 90 days

License

MIT — see repo root LICENSE.

Ver o original no GitHub

Bom para

Relacionados