grepai-trace-graphlisted

# GrepAI Trace Graph This skill covers using `grepai trace graph` to build complete call graphs showing all dependencies recursively. ## When to Use This Skill - Mapping complete function dependencies - Understanding complex code flows - Impact analysis for major refactoring - Visualizing application architecture ## What is Trace Graph? `grepai trace graph` builds a recursive dependency tree: ``` main ├── initialize │ ├── loadConfig │ │ └── parseYAML │ └── connectDB │ ├── createPool │ └── ping ├── startServer │ ├── registerRoutes │ │ ├── authMiddleware │ │ └── loggingMiddleware │ └── listen └── gracefulShutdown └── closeDB ``` ## Basic Usage ```bash grepai trace graph "FunctionName" ``` ### Example ```bash grepai trace graph "main" ``` Output: ``` 🔍 Call Graph for "main" main ├── initialize │ ├── loadConfig │ └── connectDB ├── startServer │ ├── registerRoutes │ └── listen └── gracefulShutdown └── closeDB Nodes: 9 Max depth: 3 ``` ## Depth Control Limit recursion depth with `--depth`: ```bash # Default depth (2 levels) grepai trace graph "main" # Deeper analysis (3 levels) grepai trace graph "main" --depth 3 # Shallow (1 level, same as callees) grepai trace graph "main" --depth 1 # Very deep (5 levels) grepai trace graph "main" --depth 5 ``` ### Depth Examples **--depth 1** (same as callees): ``` main ├── initialize ├── startServer └── gracefulShutdown ``` **--depth 2** (default): ``` main ├── initialize │