developer-detective

Name: developer-detective
Availability: InStock
Author: tianzecn

Diagnose code implementations and data flows using AST-based analysis.

2|Updated Dec 25, 2025

Search Tags:#context #dependencies #data-flow #callers #callees

Ready to run

npx skills add https://github.com/tianzecn/myclaudecode --skill developer-detective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: developer-detective
Source: https://github.com/tianzecn/myclaudecode/tree/main/plugins/code-analysis/skills/developer-detective
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill developer-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claudemem, and includes references (resource) components.

What problem does it solve?

This Skill helps developers understand how code works by tracing implementations, call graphs, and data flows using AST-based analysis.

Core Features & Use Cases

Implementation Discovery: locate where functions are defined and used.
Data Flow Tracing: follow callees to understand data movement.
Impact Awareness: map all usages to understand the scope of changes.

Quick Start

Find where a function is defined, then read its full context with callers and callees.

Frequently Asked Questions about developer-detective

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace function calls and dependencies in my codebase?▼

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.

Can I find all usages of a function across my project?▼

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.

How do I audit code integrations and data flow paths?▼

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.

What's the difference between AST-based analysis and text search for finding code references?▼

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.

Do I need to install additional tools to analyze code dependencies?▼

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.

When should I use data flow analysis instead of just reading code?▼

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.