Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
Passed 9 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
9 fixed4 passed either way7 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to run automated, iterative debugging cycles to catch a flaky test in test/myapp/worker_test.exs with explicit stopping criteria and iteration caps. What tool command should be invoked?
| Checked | Without skill | With skill |
|---|---|---|
| Invokes /ralph-loop:ralph-loop with --max-iterations | Missed | Passed |
The instructions your model reads when the skill loads.
Investigate bugs using the Ralph Wiggum approach: check the obvious, read errors literally.
/phx:investigate Users can't log in after password reset
/phx:investigate FunctionClauseError in UserController.show
/phx:investigate Complex auth bug --parallel
$ARGUMENTS = Bug description or error message. Add --parallel
for deep 4-track investigation.
Use parallel mode (spawn deep-bug-investigator) when:
bug mentions 3+ modules, spans multiple contexts, is intermittent
or involves concurrency, or user says --parallel/deep.
Before spawning it, determine the effective maximum nesting depth. Use an
explicit positive-integer CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH value first;
when it is unset, inspect claude --version (the default is 1 in 2.1.217–2.1.218
and 3 in 2.1.219+). If the version is unavailable, conservatively use 1. At
depth 3+, use the deep-bug-investigator orchestrator. At depth 1 or 2, keep
orchestration in this main session: spawn the four
focused tracks (reproduction, root cause, impact, fix strategy) directly in
one parallel batch, wait for all four, then synthesize their evidence. Never
spawn an orchestrator that cannot delegate.
Otherwise: Run the sequential workflow below.
Avoid confirmatory subagents: Do NOT spawn parallel subagents to "verify" findings you already identified in the main context. If Step 3-4 already identified the root cause with high confidence, present it directly — don't spend ~80K tokens on 4 subagents to
test cases passed, vs 4 / 16 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.