Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Codebase Index
Traces function dependencies using the call graph — shows callers, callees, or shortest paths between functions. Accepts function names and optional symbol IDs.
How this command is triggered — by the user, by Claude, or both
Slash command
/codebase-index:call-graphThe summary Claude sees in its command listing — used to decide when to auto-load this command
Trace function dependencies using the `call_graph` and `call_graph_path` tools. User input: $ARGUMENTS Interpret input as follows: - If input asks for a path, connection, route, chain, or "from X to Y", use `call_graph_path`. - Default to `direction="callers"` unless input asks for callees/calls/makes calls. - `name=<function>` or plain text function name sets `name`. - `symbolId=<id>` is required for `direction="callees"`. - For path queries, parse `from=<function>`, `to=<function>`, and optional `maxDepth=<number>`. Execution flow: 1. If input asks for a path and has source/target name...
Trace function dependencies using the call_graph and call_graph_path tools.
User input: $ARGUMENTS
Interpret input as follows:
call_graph_path.direction="callers" unless input asks for callees/calls/makes calls.name=<function> or plain text function name sets name.symbolId=<id> is required for direction="callees".from=<function>, to=<function>, and optional maxDepth=<number>.Execution flow:
call_graph_path with { from, to, maxDepth? }.callers, call call_graph with { name, direction: "callers" }.callees and symbolId is present, call call_graph with { name, direction: "callees", symbolId }.callees and symbolId is missing, first call call_graph with direction="callers" to get symbol IDs, then ask the user to choose one if multiple are returned.Examples:
/call-graph Database → callers for Database/call-graph callers name=Indexer → callers for Indexer/call-graph callees name=Database symbolId=sym_abc123 → callees for selected symbol/call-graph path from=createOrder to=chargeCard → shortest known path between the two symbolsIf output says no callers found, suggest running /index force first.
npx claudepluginhub helweg/opencode-codebase-index --plugin codebase-index/kasi-graphBuilds function call graph of project codebase, outputs HOTSPOTS.md summary and FUNCTIONS.jsonl data. Supports show, extract, impact, trace, cycles, dead submodes.
/coderlmExplore a codebase using tree-sitter-backed indexing to trace execution paths, find callers and implementations, and understand code structure.
/agent-brain-graphPerforms GraphRAG-powered search on code knowledge graph for relationships and dependencies between entities like functions, classes, modules, calls, imports, and inheritance.
/traceTraces the execution path of a request or operation through the codebase, mapping function calls, side effects, and failure points.
/SKILLTraces business logic flows and execution paths in code from entry points or descriptions like 'user checkout' or 'OrderService.create()'. Uses specialized modes for dead code, errors, data flow, concurrency, taint, and caching.