Show file tree of a project directory. Use instead of ls/find.

Show code structure (classes, functions, imports) for a project. Use instead of reading files to understand structure.

Get LLM-ready context for a function/class. Use INSTEAD of reading large files. Returns only relevant code.

Search files for a pattern. Faster than grep for structural searches.

Find all callers of a function (reverse call graph). Use to understand what breaks if you change a function.

Build cross-file call graph starting from a function.

Semantic code search using natural language. Use for conceptual searches like 'authentication logic' or 'payment handling'.

Detect architectural layers from call patterns. Shows high-level architecture of the project.

Pre-build call graph cache for faster queries. Run once per project before using other tldr tools.

Extract full file analysis (classes, functions, methods, imports). Use to deeply understand a single file.

Control flow graph for a function. Shows branches, loops, and execution paths.

Data flow graph for a function. Shows how data moves through variables and expressions.

Program slice: find all lines that affect a specific line. Use to understand what influences a value or statement.

Find unreachable (dead) code in a project. Useful for cleanup and refactoring.

Parse imports from a source file. Shows all dependencies of a file.

Find all files that import a module (reverse import lookup). Use to understand module usage across the project.

Find tests affected by changed files. Use before committing to know what to test.

Get type-check and lint diagnostics for a file or project. Use to find errors without running the code.