chaos-agent

Name: chaos-agent
Availability: InStock
Author: mattbutlerengineering

Seed deterministic ESLint violations to validate GitHub issue creation and closure workflows.

1|Updated Jan 24, 2026

Search Tags:#code quality #github actions #continuous improvement #chaos testing #issue filing #scheduled automation #lint monitoring

Ready to run

npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill chaos-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chaos-agent
Source: https://github.com/mattbutlerengineering/mattbutlerengineering/tree/main/.claude/skills/chaos-agent
Command: npx skills add https://github.com/mattbutlerengineering/mattbutlerengineering --skill chaos-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chaos-agent verifies that autonomous audit and lint feedback loops reliably detect and report regressions before measurement can degrade unnoticed.

Core Features & Use Cases

Synthetic lint violation seeding: Creates a non-breaking, deterministic ESLint-triggering change to validate monitoring behavior on real PRs.
Issue filing verification: Confirms the audit loop creates a GitHub issue with expected labels and a title tied to the seeded violation.
Closed-loop cleanup and logging: Closes the draft PR and verified issue and records the outcome into a state log for trend analysis across runs.

Quick Start

Invoke the skill with /chaos-agent to seed the weekly synthetic lint violation, wait for the audit loop to file an issue, then close and log the verification result.

Frequently Asked Questions about chaos-agent

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

FAQPage Schema

How do I validate that my CI lint monitoring automatically detects and files regressions?▼

Chaos testing for lint monitoring works by seeding a deterministic, non-breaking ESLint violation into a draft PR to verify that your automated audit loop successfully detects the issue, files a labeled GitHub issue, and logs the state for trend analysis.

What is chaos testing for autonomous site-audit workflows?▼

Chaos testing for autonomous site-audit workflows is the practice of deliberately injecting synthetic lint violations to prove your continuous improvement pipelines reliably catch real issues before measurement degrades unnoticed across repository workflows.

How do I test GitHub Actions issue filing automation without breaking my repository?▼

You can test GitHub Actions issue filing by creating a draft PR with a deterministic, non-breaking lint violation, waiting for the audit loop to file an expected labeled issue, and then closing the PR and issue while logging the verification result.

Can I use scheduled automation to run regression tests on my lint monitoring setup?▼

Yes, scheduled automation applies to regression testing of CI-driven lint monitoring by periodically seeding synthetic violations, verifying audit-loop detection, confirming issue creation and closure, and recording the outcome into a state log for trend analysis.

Does seeded chaos testing for code quality monitoring exfiltrate sensitive repository data?▼

No, deterministic violation seeding for code quality monitoring satisfies audit-loop detection checks, PR creation, and issue closure requirements without exfiltrating sensitive data from your repository workflows.

When do I need to verify my audit loop detection checks for continuous improvement?▼

You need to verify audit loop detection checks when you want to prove your autonomous site-audit and lint monitoring automation reliably catches real issues before measurement can degrade unnoticed across your repository workflows.