Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
Passed 17 of 22 test cases with the skill, and 11 of 22 without it.
and 4 more in the full report
7 fixed11 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
After 3 failed attempt records in `changes/legacy-parser`, the user explicitly confirmed the decision to abandon the current approach. We ran `ssf debug escalate changes/legacy-parser --decision abandon --reason 'User chose abandon' --confirm`. When should we transition the workflow state to `abandoned`?
| Checked | Without skill | With skill |
|---|---|---|
| The response transitions to abandoned state only after recording the guarded DP-5 receipt. | Missed | Passed |
The instructions your model reads when the skill loads.
Core principle: Find root cause before attempting fixes. Symptom fixes are failure.
No fixes without root cause investigation first. If you haven't completed Phase 1, you cannot propose fixes.
Use for ANY technical issue: test failures, bugs, unexpected behavior, performance problems, build failures, integration issues. Especially when under time pressure, "one quick fix" seems obvious, you've already tried multiple fixes, or you don't fully understand the issue.
Don't skip because issue "seems simple" or you're "in a hurry" — systematic debugging is faster than thrashing.
Complete each phase before proceeding.
Scientific method: form a single hypothesis ("I think X is the root cause because Y"), test with the smallest possible change (one variable at a time), verify before continuing. If it didn't work, form a NEW hypothesis — don't add more fixes. When you don't know, say so and ask for help.
test cases passed, vs 11 / 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.