What problem does it solve? Before refactoring, renaming, or changing a function's signature, developers need to know every place that function is called. Manually searching a large codebase is slow and error-prone, and plain text search returns false positives. This Skill uses GrepAI's call-graph tracing to answer "who calls this function?" with precise file, line, and context information. ## Core Features & Use Cases - Caller Tracing: Run grepai trace callers "FunctionName" to list every call site with file path, line number, and surrounding context. - Multiple Output Formats: Human-readable output, --json for scripting, compact JSON for AI token efficiency, and TOON format for ~50% fewer tokens. - Extraction Modes: Choose fast regex-based mode or precise tree-sitter AST parsing for higher accuracy across Go, JavaScript, TypeScript, Python, Rust, Java, C/C++, and more. - Use Case: Before renaming getUserById, run the trace to enumerate all callers, then pipe JSON output through jq to get a unique list of affected files for your refactor plan. ## Quick Start Ask the AI to find all callers of a function, for example: "Use grepai trace callers to show me everywhere the Login function is called in this repository."
