Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-trace
Trace Elixir call trees from entry points via mix xref.
Passed 18 of 22 test cases with the skill, and 15 of 22 without it.
and 1 more in the full report
4 fixed14 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
During a call tree analysis of `MyApp.Legacy.process/1`, the traversal hits level 11. What action and diagnosis should be rendered for this call chain?
| Checked | Without skill | With skill |
|---|---|---|
| Truncates traversal at depth 10 due to architectural issue limits. | Missed | Passed |
The instructions your model reads when the skill loads.
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 the caller query first, then inspect another function in the chain as needed:
mix xref callers MyApp.Accounts.update_user/2
mix xref callers MyApp.Accounts.get_user/1
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 |
test cases passed, vs 15 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.