flake-vs-bug-triage
Skill1 starsChanged 3 months agoMITView on GitHub
Decide if a failing test is flaky or a real regression. Use on intermittent CI failures, or Chinese "flaky", "偶发失败", "是不是不稳定测试". Practical triage workflow.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-diff-ship-checkSkill
- customer-bug-to-failing-testSkill
- dead-code-safe-deleteSkill
- env-drift-checkSkill
- feature-flag-lifecycleSkill
- minimal-repro-packSkill
- secret-redact-before-aiSkill
- using-ship-guard-skillsSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Stop endless re-run loops.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Flake vs Bug Triage
Overview
Don’t “re-run until green” forever. Classify failure, quarantine or fix with evidence.
Signals
| Prefer flake | Prefer real bug |
| Passes on re-run same commit | Fails consistently same commit |
| Timing/order/network race | Deterministic assertion on logic |
| Shared mutable global state | Clear code path regression |
| Only one shard/environment | Multiple envs same fail |
Steps
- Capture: test name, log excerpt, commit SHA, first fail time.
- Reproduce locally (N runs). Record pass/fail count.
- Classify: flake | bug | infra | unknown.
- Actions:
- flake → quarantine ticket + stabilize plan (not delete assert silently)
- bug → root cause + fix + test
- infra → env/owners
- Stop endless re-run loops; set max re-run policy.
Exit criteria
- Evidence of consistency (or lack)
- Classification
- Next action owner-ready
- No silent deletion of coverage
Anti-patterns
- Merge with failing test “it’s flaky” without ticket
- Deleting the test to green CI
Output template
## Triage
- Test: ...
- Runs: pass=… fail=…
- Class: flake | bug | infra | unknown
- Action: ...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.