Skip to content

oliver-kriska/claude-elixir-phoenix / targets/dsh/skills/phx-investigate

phx-investigate

Verified

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

FileKindSize
SKILL.mdskill md4.0 KB
references/debug-commands.mdmarkdown2.0 KB
references/error-patterns.mdmarkdown1.4 KB
references/investigation-template.mdmarkdown998 B

references/investigation-template.md

View on GitHub
# Investigation Output Template

Return this structure in the current session; do not write a report file unless the user explicitly asks for one:

````markdown
# Bug Investigation: <bug description>

## Error

```
{exact error message}
```

## Reproduction

```bash
{command to reproduce}
```

## Ralph Wiggum Checklist

- [x] File saved? YES
- [x] Compiled? YES
- [ ] Correct key type? **NO - FOUND IT**
- [ ] Data exists? Not checked

## Root Cause

**What's wrong**: Using string key "user_id" but map has atom :user_id

**Where**: lib/my_app_web/controllers/user_controller.ex:45

**Why missed**: External API returns string keys, internal code uses atoms

## Fix

```elixir
# Before
def show(conn, %{"user_id" => id}) do
  user = Accounts.get_user(params["user_id"])  # params has string keys!

# After
def show(conn, %{"user_id" => id}) do
  user = Accounts.get_user(id)  # Already extracted
```

## Prevention

- Add test with external API mock
- Add typespec to catch at compile time
````
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexUnverifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall