qa-resilience-fault-injection

Inject bounded, named faults to assess system resilience during stress tests.

Updated May 28, 2026
One-click install
npx skills add https://github.com/SensLiao/Claude-code-setting --skill qa-resilience-fault-injection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-resilience-fault-injection
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/qa-resilience-fault-injection
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill qa-resilience-fault-injection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the simulation of various fault scenarios to test system resilience, ensuring it can gracefully handle disruptions.

Core Features & Use Cases

  • Fault Injection: Simulate network issues, resource pressure, and other faults.
  • Observation & Analysis: Record system behavior under stress.
  • Staged Execution: Run experiments in a controlled environment.

Quick Start

Use the qa-resilience-fault-injection skill to inject a latency fault into the 'checkout' endpoint.

Frequently Asked Questions about qa-resilience-fault-injection

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

FAQPage Schema
How does chaos engineering fault injection validate system resilience?

Chaos engineering validates system resilience by automating fault injection within a bounded blast radius and verifying that steady-state hypotheses are maintained during stress tests.

How do I automate fault injection for resilience testing on a specific endpoint?

You can automate fault injection for resilience testing by triggering a named latency fault on your target endpoint, allowing the system to execute controlled stress tests while recording behavior under pressure.

Can I use resilience testing scripts to inject a latency fault into a checkout endpoint?

Yes, you can use the provided scripts to inject a latency fault into a checkout endpoint, running the experiment in a controlled environment to observe system behavior under simulated stress.

What is the best way to ensure safe rollback procedures during system verification stress tests?

The best way to ensure safe rollback during system verification is to use bounded, named faults that limit the blast radius, ensuring robust rollback procedures are triggered if steady-state hypotheses are violated.

When should I not use fault injection for steady-state analysis?

You should not use fault injection for steady-state analysis if your environment lacks controlled boundaries, as unbounded faults can exceed the defined blast radius and compromise robust rollback procedures.