developer-detective

Trace function calls and dependencies using AST-based analysis to map callers and callees. This approach locates exact file:line references and follows data movement through your code without text-based searching, enabling precise impact assessment and change scope visibility.

Yes. AST-based analysis locates all usages and implementation sites with exact file:line coordinates. This discovers both direct callers and nested dependencies, critical for understanding change impact before refactoring.

Audit integrations by analyzing call graphs and data flow using AST parsing. Map all entry and exit points, trace how data moves between functions, and report full context to assess whether integrations are correct and complete.

AST-based analysis parses code structure to identify semantic relationships—actual function definitions and calls—avoiding false positives from comments and string literals. Text search matches any occurrence, leading to noise and missed context in complex codebases.

The Skill uses claudemem v0.3.0 for dependency and usage analysis, handling AST parsing and call-graph construction. No additional analysis tools are required; dependencies are managed as part of the Skill.

Use data flow analysis when understanding sprawling implementations, multi-layer call chains, or impact scope for changes. Manual reading misses hidden paths and callers; systematic tracing ensures complete context for large refactors or security audits.