Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →florianbruniaux/investigate
Systematic root-cause debugging: find the cause before writing any fix
Passed 18 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed14 passed either way3 still failing1 broke5 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
In Phase 6 (Hypothesis testing), an engineer added a temporary console diagnostic log to verify Hypothesis #1 for a bug in `src/api/cart.ts`. The log output showed that Hypothesis #1 was wrong. What is the immediate required action?
| Checked | Without skill | With skill |
|---|---|---|
| The response instructs gathering more evidence and returning to code reading without guessing. | Missed | Passed |
The instructions your model reads when the skill loads.
Systematic debugging with mandatory root cause investigation before any code changes.
Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Fixing symptoms creates whack-a-mole debugging. Every fix that doesn't address root cause makes the next bug harder to find.
Gather all available context before forming any hypothesis.
Output: A precise symptom statement: what fails, when, with what error.
Trace the code path from symptom back to potential causes. Do not guess.
# Find all references to the failing component
grep -rn "ComponentName\|function_name\|error_string" src/ --include="*.{ts,js,py,rb,go}" | head -30
# Check recent changes to affected files
git log --oneline -15 -- <affected-file>
# Read the actual diff for each recent commit
git show <commit-hash> -- <affected-file>
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.