How does it differ from a standard grep search?

It uses 'mix xref callers' as its primary authoritative source, providing a more accurate and structured view of code dependencies than simple text searching.

Where is the call tree output saved?

The resulting analysis is automatically saved as a markdown file within the .claude/plans directory of your project for easy documentation and reference.

What are entry points in this context?

Entry points are the boundaries of your application logic where external requests or processes begin, such as Phoenix Controllers, LiveView callbacks, Oban workers, and GenServer handles.

Can it handle circular dependencies?

Yes, the skill tracks visited Module-Function-Arguments (MFAs) to prevent infinite loops and ensure the recursive tracing process remains stable.

What is the call-tracing skill for Claude Code?

It is a specialized capability for Elixir/Phoenix that builds recursive call trees to show how specific functions are reached from entry points like Controllers or LiveViews.

Elixir Call Tracing

Name: Elixir Call Tracing
Author: oliver-kriska

byoliver-kriska

•

API Development

Builds comprehensive recursive call trees to map how Elixir functions are invoked from system entry points.

The Elixir Call Tracing skill enables developers to visualize data flow and execution paths within Phoenix applications by mapping how specific functions are reached from Controllers, LiveView callbacks, and background workers. By utilizing parallel subagents and the authoritative mix xref tool, it identifies call patterns, extracts argument types, and prevents circular logic loops, making it an essential tool for debugging complex state changes, refactoring function signatures, and understanding legacy codebases.

Key Features

01Detailed argument pattern extraction and MFA tracking to prevent circular loops

0262 GitHub stars

03Parallel category tracing with specialized subagents for HTTP and WebSocket paths

04Recursive call tree generation using mix xref

05Automated research output saved to structured markdown files

06Automatic entry point identification for Controllers, LiveView, and Oban

Use Cases

01Debugging incomplete stack traces by visualizing the full execution path from entry points

02Tracing the origin of unexpected nil values or runtime errors through the call stack

03Mapping dependencies and caller patterns before refactoring function signatures

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add oliver-kriska/claude-elixir-phoenix call-tracing

For use in Claude.ai and ChatGPT

Download Skill