quality-chaos-monkey

Trace code paths to identify bugs, logic errors, and race conditions.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill quality-chaos-monkey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-chaos-monkey
Source: https://github.com/zcaceres/skills/tree/main/skills/quality-chaos-monkey
Command: npx skills add https://github.com/zcaceres/skills --skill quality-chaos-monkey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the difficulty of identifying edge-case bugs, race conditions, and logic errors that are often missed during standard code reviews.

Core Features & Use Cases

  • Static Path Analysis: Systematically traces code paths across 10 chaos categories including boundary inputs, state consistency, and error handling.
  • Runtime Browser Testing: Escalates to Playwright or Chrome DevTools to stress-test frontend components, UI interactions, and network resilience.
  • Structured Reporting: Generates detailed markdown reports with file-line citations, confidence ratings, and concrete reproduction steps.

Quick Start

Trigger the quality-chaos-monkey skill to audit the current directory for potential logic errors and edge cases.

Frequently Asked Questions about quality-chaos-monkey

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

FAQPage Schema
How do I systematically trace code paths to find edge-case bugs and race conditions?

Systematic code path tracing identifies edge-case bugs and race conditions through static analysis across ten chaos categories, including boundary inputs and state consistency, to catch logic errors missed in standard code reviews.

What is chaos engineering for frontend testing and how does it apply to UI resilience?

Chaos engineering for frontend testing stress-tests UI interactions and network resilience by escalating static path analysis to runtime browser testing, dynamically verifying complex frontend components under adverse conditions.

Do I need Playwright or Chrome DevTools to perform runtime browser testing for bug finding?

Runtime browser testing for bug finding requires integration with Playwright or Chrome DevTools to dynamically verify complex UI and network-dependent code paths during static path analysis escalation.

How do I generate structured reports for static analysis and bug reproduction?

Structured reports for static analysis generate detailed markdown outputs containing file-line citations, confidence ratings, and concrete reproduction steps to document discovered logic errors and edge cases.

What are the limitations of static path analysis for finding race conditions?

Static path analysis limitations emerge when verifying network-dependent code paths, requiring runtime browser testing via Playwright or Chrome DevTools to dynamically confirm race conditions and frontend state inconsistencies.

Can I use quality-chaos-monkey to audit my current directory for potential logic errors?

Auditing your current directory for potential logic errors triggers static path analysis to systematically trace code paths, identifying boundary input vulnerabilities, state consistency issues, and error handling defects.