Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →magebyte-zero/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 14 of 18 test cases with the skill, and 7 of 18 without it.
and 5 more in the full report
8 fixed9 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are running a lightweight tweak workflow to debug a minor UI glitch. Do we need to generate a formal execution plan via execution recommend before recording a debug attempt?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that lightweight tweak workflows maintain a planless contract where the valid workflow receipt authorizes debugging without requiring a formal execution plan. | Missed | Passed |
The instructions your model reads when the skill loads.
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Core principle: Find root cause before attempting fixes. Symptom fixes are failure.
Investigate in executing without a phase transition or a separate debug ledger: reproduce, trace the root cause, make one focused repair and verify. Keep useful failure evidence in the existing progress entry. Three failures for the same unresolved issue warrant a decision; unrelated findings do not accumulate a shared budget. No task book or subagent is required. The detailed legacy protocol below is for an existing debugging state or an investigation that needs it.
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.
test cases passed, vs 7 / 18 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.