analyze
무료Analyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature…
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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 |
def handle_call/3, def handle_cast/2 | GenServer |
Trace controller, LiveView, worker, and internal entry-point categories in this
session, starting each category with mix xref callers. Native generic workers
may handle independent categories in parallel when the runtime provides them,
but the same-session sequential path is fully supported and must produce the
same call tree. Do not require a named custom agent or Claude-specific spawn
configuration.
.claude/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아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Analyze a legacy app in any language before rewriting it in Elixir: inventory, features as goals, why each mechanism exists, runtime topology, external contracts. Use to start or refresh a rewrite.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design the idiomatic Elixir architecture for a rewrite: set the compatibility bar (ADR-000), consult phx specialists on open questions, then build contexts, ledger and ADRs. Use after /rewrite:analyze.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ash Framework — resources, actions, policies, aggregates; Use when generating resources via mix ash.codegen, editing…
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compatibility alias for the Elixir/Phoenix plugin's LiveView assigns audit. Invoke explicitly with /lv:assigns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates. Use when LiveView memory grows or you need to add temporary_assigns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.