developer-detective

Data flow tracing follows function call chains using AST analysis to map how data moves between callees. Developer-detective identifies each function in the chain and its exact file:line location, helping you understand data movement and dependencies across your implementation.

Finding all function usages requires enumerating callers—every location that invokes a target function. Developer-detective uses AST callers analysis to return a complete list with file:line references, essential for impact analysis before modifying shared code.

Impact analysis examines both callers (who depends on this function) and callees (what this function depends on) to predict change consequences. Developer-detective traces these relationships through AST analysis and outputs exact locations, letting you evaluate scope before refactoring.

AST analysis requires claudemem v0.3.0 in raw mode to produce precise context. The Skill disables grep, find, and glob to ensure accurate caller and callee extraction with exact file:line results instead of approximate pattern matches.

Finding function definitions uses AST references to pinpoint implementation location by file and line number. Developer-detective traces the definition directly, bypassing search approximation to give you the exact source location for any symbol.

Dependency auditing traces callees—functions your code invokes—to map integrations and external dependencies. Developer-detective lists every callee with precise locations, helping you audit what your implementation relies on and identify integration points.