qa-flaky
Skill0 starsChanged 28 days agoMITView on GitHub
Diagnose and fix flaky / intermittent / CI-only test failures at the root cause — reproduce with repeat, parallel, shuffled and timezone runs, classify the cause, fix it without retries or sleeps, and prove 0 failures after.
In this repository10 other files it gives its agents.
- qa-auditSkill
- qa-automateSkill
- qa-bugSkill
- qa-casesSkill
- qa-diffSkill
- qa-exploreSkill
- qa-initSkill
- qa-planSkill
- qa-releaseSkill
- qaSkill
The file
Files
Delegate to the qa-flaky-doctor subagent (it may appear as argus-qa:qa-flaky-doctor) with: $ARGUMENTS, the test commands from .qa/context.md, and any CI log excerpt the user shared.
Report back: the root cause, the before/after failure rates, the fix, and whether it's actually a product bug (if so, offer /qa-bug).
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
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.