test-failure-triage
Skill0 starsChanged 11 days agoMITView on GitHub
Use when a test fails or a run needs diagnosis. Gather evidence before classifying product, stale test, data, environment, or accessibility failures; preserve assertions and coverage instead of forcing a green result.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- CheckPickerUpper/skillstheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- CheckPickerUpper/skills★ 9same 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 repository34 other files it gives its agents.
- chatgpt/AGENTS.mdAGENTS.md
- opencode/AGENTS.mdAGENTS.md
- zcode/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- agent-doc-authoringSkill
- agent-experienceSkill
- ai-image-promptsSkill
- api-behavior-flowSkill
- architecture-and-performanceSkill
- behavioral-testingSkill
- behavior-auditSkill
- browser-tabs-uiSkill
- code-qualitySkill
- context-compactSkill
- design-principlesSkill
- design-to-deliverySkill
- design-validationSkill
- e2e-test-authoringSkill
- engineering-reviewSkill
- excalidrawSkill
- external-ai-consultSkill
- google-omni-videoSkill
- llm-agent-tool-disciplineSkill
- parallel-subagentsSkill
- qa-test-scenariosSkill
- reliable-executionSkill
- research-and-reuseSkill
- server-security-hardeningSkill
- session-handoffSkill
- shadcn-librarySkill
- sudo-handoffSkill
- task-intakeSkill
- tauri-v2-docsSkill
- user-behavior-flowSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read the actual error, expected/received output, trace or page snapshot, test, implementation and environment/config under test.
- Very specific: line 25
Never remove assertions, conditionalize them, broaden matches, add arbitrary delays, hide strict-mode errors with .first(), or accept …
≈ “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
Test failure triage
Purpose
Explain a failing run accurately and repair only the verified cause within authorized scope.
When to use
Red tests and release verification. Project triage skills and modification boundaries take precedence.
Preconditions
Read the actual error, expected/received output, trace or page snapshot, test, implementation and environment/config under test. Do not upload confidential traces.
Workflow
- Record the symptom and reproduce the smallest affected case in isolation when safe.
- Classify with evidence: product = implementation violates the intended contract; stale = a confirmed intentional contract change; data = independently verified missing/wrong fixture; environment = evidence of infrastructure failure; accessibility = inspected missing/incorrect accessible contract. Unknown stays unresolved, not automatically stale.
- A timeout alone proves none of these. An isolated pass is evidence of intermittency, not proof of its root cause; compare logs/trace and environment before claiming contention.
- Repair the verified cause only. For a test-only repository, respect product edit restrictions and report product bugs. Do not add missing product behavior by changing expectations.
- Re-run the affected case, and affected callers when helpers/contracts changed. Keep known blockers enumerated; mark skips with a reason only when permitted.
Rules
Never remove assertions, conditionalize them, broaden matches, add arbitrary delays, hide strict-mode errors with .first(), or accept unreviewed snapshots to clear a failure. Distinguish pre-existing failure from regression with history/evidence.
Common mistakes
Calling timeout “flaky”; declaring environment from one pass; reporting skipped coverage as green; silently deleting a blocked test.
Validation
Report symptom, evidence, verdict or unresolved uncertainty, changes, and actual rerun result. Separate passed, failed, skipped and not run. Explain any untested area.
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.