Agent skill

phx-investigate

Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-investigate --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 4 KB
Bundled scripts: none
Path: targets/opencode/skills/phx-investigate/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Investigate Bug Investigate Elixir/Phoenix bugs root-cause first. Reproduce or establish the failing behavior before recommending a fix, and cite concrete paths and lines. ## Usage ```text /phx-investigate Users can't log in after password reset /phx-investigate FunctionClauseError in UserController.show /phx-investigate Complex auth bug --parallel ``` Treat the text after the skill name as the bug description. `--parallel` asks for independent investigation tracks when native OpenCode subagent tooling is available; it is an optimization, never a requirement. ## Iron Laws 1. **Read the error literally first** — extract the exception, message, failing assertion, and first relevant application frame before theorizing. 2. **Check the obvious before going deep** — compile errors, missing migrations, atom/string mismatches, nil values, stale servers, and changeset errors explain many failures. 3. **Reproduce before proposing a fix** — run the smallest relevant test or controlled command and record its output. If reproduction is impossible, state exactly what evidence establishes the failure instead. 4. **Confirm the root cause with evidence** — distinguish the observed failure, the ca

What's inside
Steps it walks through
  1. Usage
  2. Iron Laws
  3. Workflow
  4. 1. Consult Existing Evidence
  5. 2. Capture Runtime Context When Available
  6. 3. Run Sanity Checks
  7. 4. Reproduce Before Fixing
  8. 5. Check the Obvious
  9. 6. Trace and Test the Hypothesis
  10. 7. Report
  11. References
Ships with 3 files
  • references/debug-commands.md
  • references/error-patterns.md
  • references/investigation-template.md
Commands it runs
mix compile --warnings-as-errors
mix test test/path_test.exs --trace
More from claude-elixir-phoenix
All skills →
About this skill
What does the phx-investigate skill do?

Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native OpenCode subagents only when useful.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-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.

Keep going