Call Graph Operations

Build and query call graphs showing which functions call which.

When to use

Use this skill when the user asks:

•"Build a call graph for this project"
•"What does function X call?" / "What are the callees of X?"
•"What calls function X?" / "What are the callers of X?"
•"Show me the full call graph"

How to invoke

Invocation: Use the claudit CLI only. Do not run python -m claudit.skills.graph.

bash

claudit graph build <project_dir> [--language c|java|python] [--overrides path.json] [--force]
claudit graph show <project_dir>
claudit graph callees <function> <project_dir>
claudit graph callers <function> <project_dir>

Subcommand syntax: Use callees and callers as subcommands, not flags. Wrong: claudit graph query --callees <func> or --callers <func> (there is no graph query subcommand). Correct: claudit graph callees <func> <dir>, claudit graph callers <func> <dir>.

Flags: --language is accepted only by graph build. graph callees and graph callers do not accept --language; language is inferred from the cached index.

python

from claudit.skills.graph import build, show, callees, callers

Notes

•Building the call graph is the most expensive operation — it indexes every symbol, extracts function bodies, and tokenizes them with Pygments.
•Results are cached in .cache/ keyed on GTAGS mtime. Use --force to rebuild.
•Manual overrides JSON can supplement static analysis for dynamic dispatch, callbacks, etc.
•When path finding returns 0 paths (e.g. due to Java interface/impl or other missing edges), use graph callees and graph callers plus manual source inspection as in the path skill's "When path find returns no paths" workflow.