Menu
Trace Elixir call paths from entry points with `mix xref`.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Recommend the right `$elixir-phoenix-*` skill for the current task.
Elixir/Phoenix: Review lifecycle, state-machine, Oban, persistence, pause/resume, retry, and restart-sensitive changes before commit, push, or PR. Use for concurrency-sensitive runtime work to produce explicit blocking vs optional findings, require durability checks, and verify smoke plus restart resilience when applicable.
Capture a solved Phoenix problem as a reusable solution doc.
Audit LiveView assigns for memory bloat, dead assigns, and stream candidates.
Audit project health across architecture, security, performance, tests, and deps.
Analyze Phoenix context boundaries and coupling with `mix xref`.
| name | elixir-phoenix-call-tracing |
| description | Trace Elixir call paths from entry points with `mix xref`. |
| metadata | {"short-description":"Trace Elixir call paths with xref"} |
Build call trees showing how functions are reached from entry points.
mix xref callers first - It's authoritative; grep is fallback only| Condition | Why Call Tree Helps |
|---|---|
| Unexpected nil/value at runtime | Trace where the value originates |
| Bug can't reproduce locally | See all entry points that reach the code |
| Changing function signature | Find all callers and their argument patterns |
| Incomplete stack trace | Get full path context |
| "Where does X come from?" | Visual answer to data flow question |
Run mix xref callers MyApp.Accounts.update_user/2 to find all callers. Then read the reported locations to see argument patterns.
| Pattern | Type |
|---|---|
def mount/3, def handle_event/3 | LiveView |
def index/2, def show/2, def create/2 | Controller |
def perform(%Oban.Job{}) | Oban Worker |
def handle_call/3, def handle_cast/2 | GenServer |
For full recursive trees with argument extraction and parallel category tracing,
run the call-tracer workflow with a focused function target in MFA format
(Module:function/arity), for example: MyApp.Accounts:update_user/2.
The call-tracer agent uses parallel subagents for each entry point category:
Each gets fresh 200k context for deep exploration.
.codex/plans/{slug}/research/call-tree-{function}.md
For detailed patterns:
references/mix-xref-usage.md - Full mix xref commands and optionsreferences/entry-points.md - All Phoenix/OTP entry point patternsreferences/argument-extraction.md - AST parsing for argument patterns