Failure triage
Skill lubochka/xiigen-general-skills/claude/skills/failure-triage
Open-source AI agent skills for safer Claude, Codex and Cursor coding workflows
npx -y skills add lubochka/xiigen-general-skills --skill failure-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Classify failures before changing implementation. Use after failed builds, tests, commands, or smoke checks.
SKILL.md
0.8 KB, 158 tokens by cl100k_base, as published. Nobody here has run it
Failure Triage
Purpose
Classify failures before changing implementation.
When to Use
Use after failed builds, tests, commands, or smoke checks.
Inputs
Failure output, environment, recent changes, expected behavior.
Steps
- Capture the symptom.
- Classify likely source: code, test, environment, data, flaky behavior, or command misuse.
- Choose the smallest next check.
- Avoid broad rewrites until cause is narrowed.
Gates
There is a probable cause and next diagnostic step.
Evidence
Failure logs, narrowed hypothesis, and targeted check result.
Anti-Patterns
Fixing blindly; changing multiple variables at once.
Related
root-cause-tracing, systematic-debugging
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most debug triage skills give in 158 tokens
Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07
- Investigate root cause before proposing any fixin 102 of 839, across 67 files
- Read error messages completelyin 89 of 839, across 49 files
- Create a failing test case before fixingin 84 of 839, across 46 files
- Reproduce the issue consistentlyin 82 of 839, across 41 files
- Change one variable at a timein 82 of 839, across 42 files
- Check recent changesin 74 of 839, across 36 files
- Write the regression test before fixingin 74 of 839, across 40 files
- Fix the root cause not the symptomin 60 of 839, across 45 files
- Implement a single fix at a timein 59 of 839, across 20 files
- Trace data flow backward to the sourcein 50 of 839, across 20 files
- Remove all debug instrumentationin 49 of 839, across 13 files
- Form a single hypothesisin 48 of 839, across 18 files
Said here and by no other author read
- capture the symptom
- classify the likely source
- choose the smallest next check
- narrow the cause before fixing
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.