AnjanJAnjanJ/rails_error_dashboard/.claude/skills/chaos/SKILL.md

chaos

Skill93 starsChanged 8 days agoMITView on GitHub

Run pre-release chaos tests — real Rails apps in production mode

4 other projects use a version of this.

Adopted by

Most recently taken up by

nitinjain999/platform-skillstheir own version, first seen Oct 13, 2026
SwitchbackTech/compasstheir own version, first seen Oct 8, 2026
CHAOSX-SPACE/god-of-the-voidtheir own version, first seen Sep 5, 2026
Jkudjo/oh-my-cursortheir own version, first seen Apr 3, 2026

Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
SwitchbackTech/compass★ 227same name
nitinjain999/platform-skills★ 71same name
CHAOSX-SPACE/god-of-the-void★ 1same name
Jkudjo/oh-my-cursor★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-breadcrumb-pageSkill
- cqrs-patternsSkill
- demo-updateSkill
- host-app-safetySkill
- new-featureSkill
- release-rulesSkill
- releaseSkill
- roadmap-statusSkill
- safety-checkSkill
- testSkill

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Run integration tests that create real Rails apps in /tmp, install the gem, and run in production mode.
line 9
Distinctive:
If failures occur, show the failing phase and assertion details
line 64
Very specific:
ALL apps run in RAILS_ENV=production
line 70
Distinctive:
ALL features enabled (analytics, source code, git blame, webhooks, rate limiting)
line 71

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

/chaos — Pre-Release Chaos Tests

Run integration tests that create real Rails apps in /tmp, install the gem, and run in production mode.

Usage

/chaos or /chaos all — all 4 core apps (~4-5 min, ~1,480 assertions; the summary counts 5 runs because the HTTP app records two)
/chaos release — full release audit, 8 apps (~12-15 min, 2100+ assertions)
/chaos sync — sync config only (~1 min)
/chaos async — async (Sidekiq inline) + shared DB
/chaos http — HTTP middleware capture + dashboard
/chaos separate — separate database config

Commands

All Core Apps (Lefthook Default)

bin/pre-release-test all

Full Release Audit

bin/pre-release-test release_audit

Individual Apps

bin/pre-release-test full_sync
bin/pre-release-test full_async
bin/pre-release-test full_http
bin/pre-release-test full_separate_db

Additional Release Audit Apps

bin/pre-release-test full_kitchen_sink
bin/pre-release-test full_multi_app
bin/pre-release-test full_solid_queue
bin/pre-release-test full_upgrade

Test Phases

Each app runs through these phases:

Phase	What It Tests
A	Data integrity — error logging, deduplication, occurrence counts
B	Edge cases — nil values, huge payloads, unicode, concurrent writes
C	Query layer — filters, sorting, pagination, analytics queries
D	Dashboard HTTP — all controller endpoints return 200
E	Subscriber capture — `Rails.error.report()` with 20+ error types
F	HTTP middleware — starts Puma, hits endpoints via curl, verifies capture

After Running

Report pass/fail summary and assertion counts
If failures occur, show the failing phase and assertion details
Phase F failures often indicate stale Puma processes — check with lsof -ti :<port>

Notes

Apps are created in /tmp/pre_release_test_$$ (auto-cleaned)
ALL apps run in RAILS_ENV=production
ALL features enabled (analytics, source code, git blame, webhooks, rate limiting)
Phase F starts a real Puma server — always kills stale servers first
Templates: test/pre_release/templates/full_*_initializer.rb
Test harness: test/pre_release/lib/test_harness.rb

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free