chaos-monkey

Trace code paths and run browser tests to identify bugs and race conditions.

7|Updated May 28, 2026

Search Tags:#testing #quality assurance #static analysis #debugging #edge cases #chaos engineering

Ready to run

npx skills add https://github.com/zcaceres/skills --skill chaos-monkey-zcaceres

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chaos-monkey
Source: https://github.com/zcaceres/skills/tree/main/plugins/quality/skills/chaos-monkey
Command: npx skills add https://github.com/zcaceres/skills --skill chaos-monkey-zcaceres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of manually identifying hidden logic errors, race conditions, and edge-case vulnerabilities in complex codebases by providing a structured, adversarial testing framework.

Core Features & Use Cases

Static Path Analysis: Systematically traces code paths, including error handling and async flows, to identify potential failures before they occur.
Runtime Browser Testing: Leverages Playwright and DevTools to simulate real-world user interactions, network failures, and state corruption in frontend applications.
Use Case: Use this skill to audit a critical authentication module or a complex frontend checkout flow to ensure it handles invalid inputs, race conditions, and network errors gracefully.

Quick Start

Ask the chaos monkey to perform a full quality audit on the user authentication module located in the src/auth directory.

Frequently Asked Questions about chaos-monkey

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

FAQPage Schema

How do I systematically probe my code for bugs and edge cases?▼

To probe code for bugs and edge cases, you can use an adversarial testing framework that systematically traces code paths, including error handling and async flows, to identify logic errors and race conditions through static analysis and runtime browser testing.

What is chaos engineering and how does it apply to static path analysis?▼

Chaos engineering for static path analysis involves systematically tracing code paths, including error handling and async flows, to identify potential failures and hidden logic errors before they occur in complex codebases.

Does this code auditing approach require Playwright or Chrome DevTools to run?▼

Yes, browser-based runtime verification and path exploration require integration with Playwright or Chrome DevTools to simulate real-world user interactions, network failures, and state corruption in frontend applications.

How do I audit a frontend checkout flow for race conditions and network errors?▼

You can audit a frontend checkout flow by simulating real-world user interactions, network failures, and state corruption using Playwright and Chrome DevTools to ensure the application handles invalid inputs and race conditions gracefully.

What's the best way to validate security boundaries in an authentication module?▼

The best way to validate security boundaries in an authentication module is using a structured quality audit that traces static code paths and exercises runtime browser testing to ensure invalid inputs and edge-case vulnerabilities are handled gracefully.

When should I not use chaos engineering for quality assurance?▼

You should avoid chaos engineering for quality assurance when a codebase lacks complex async flows or frontend browser interactions, as the framework relies on Playwright and DevTools integration to simulate real-world state corruption and network failures.