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.
npx skills add oliver-kriska/claude-elixir-phoenix --skill investigate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Investigate Bug Investigate bugs using the Ralph Wiggum approach: check the obvious, read errors literally. ## Usage ``` /phx:investigate Users can't log in after password reset /phx:investigate FunctionClauseError in UserController.show /phx:investigate Complex auth bug --parallel ``` ## Arguments `$ARGUMENTS` = Bug description or error message. Add `--parallel` for deep 4-track investigation. ## Mode Selection 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
- Usage
- Arguments
- Mode Selection
- Iron Laws
- Investigation Workflow
- Step 0: Consult Compound Docs
- Step 0a: Runtime Auto-Capture (Tidewave -- PRIMARY when available)
- Step 1: Sanity Checks
- Step 2: Reproduce
- Step 3: Read Error LITERALLY
- Step 4: Check the Obvious (Ralph Wiggum Checklist)
- Step 5: IO.inspect / Tidewave projecteval
- Step 6: Identify Root Cause
- Step 7: Hand Off
What does the investigate skill do?
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill investigate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.