Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Investigate Bug · oliver-kriska | DecimalAI

codingby oliver-kriska

Investigate Bug

oliver-kriska/phx-investigate

Source oliver-kriska/claude-elixir-phoenix ↗License MIT

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

SkillScore70Maintained

Automatic

Coding pack

Last verified 9/3/2026

What it changes

Passed 12 of 17 test cases with the skill, and 11 of 17 without it.

Without skill65%

With skill70%

Checks it passed that the model alone missed

The response checks for stale server instances before investigating socket code.
The response specifies inspecting rendered validation errors before browser assets.
The response notes that a missing `.claude/solutions/` directory does not block the workflow.

and 1 more in the full report

3 fixed13 passed either way5 still failing2 broke

Pass-rate lift: +4 pp
Tokens: +12%
Agent turns: 0%
Response time: -18%

Model gemini-3.6-flashMeasured 9/3/2026v616 of 23 cases passed with skill · 17 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/oliver-kriska-phx-investigate/SKILL.md https://app.decimal.ai/s/oliver-kriska-phx-investigate/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add oliver-kriska-phx-investigate, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/oliver-kriska-phx-investigate/ and pins it in .decimal/skills.lock

decimalai skills add oliver-kriska-phx-investigate

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/oliver-kriska-phx-investigate/SKILL.md https://app.decimal.ai/s/oliver-kriska-phx-investigate/SKILL.md

Raw file: /s/oliver-kriska-phx-investigate/SKILL.md ↗ · machine-readable summary at /s/oliver-kriska-phx-investigate.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 3

Prompt

Before running new test suites during an investigation, what local repository artifacts and historical solution locations should be searched first?

What was checked, without and with the skill
Checked	Without skill	With skill
The response checks recent git diffs and existing test logs.	Passed	Passed
The response notes that a missing `.claude/solutions/` directory does not block the workflow.	Missed	Passed

case-17 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md99 lines4 files

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

/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 DeepSeek Harness subagent tooling is available; it is an optimization, never a requirement.

Iron Laws

Read the error literally first — extract the exception, message, failing assertion, and first relevant application frame before theorizing.
Check the obvious before going deep — compile errors, missing migrations, atom/string mismatches, nil values, stale servers, and changeset errors explain many failures.
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.
Confirm the root cause with evidence — distinguish the observed failure, the causal code path, and the proposed correction.
Do not edit while investigating unless the user asks for a fix — the investigation result is evidence and a recommendation, not an implicit patch.

Workflow

1. Consult Existing Evidence

Search .claude/solutions/, recent diffs, tests, logs, and the literal error. Do not block if .claude/solutions/ does not exist.

2. Capture Runtime Context When Available

Track record

Benchmark

12 / 17

test cases passed, vs 11 / 17 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/2/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

oliver-kriska / claude-elixir-phoenix

targets/amp/skills/phx-investigate/SKILL.md

View on GitHub ↗

License MITImported 9/2/2026Version v6Bundled 3 files

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

oliver-kriska/investigateInvestigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.Close match+32 pp pass-rate lift

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Investigate Bug

Usage

Iron Laws

Workflow

1. Consult Existing Evidence

2. Capture Runtime Context When Available

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills