developer-detective

Name: developer-detective
Availability: InStock
Author: MadAppGang

Traces data flow and function call relationships via AST analysis to locate implementations and assess impacts.

278|29|Updated Nov 4, 2025

Search Tags:#implementation #data-flow #callers #impact #callees

Ready to run

npx skills add https://github.com/MadAppGang/claude-code --skill developer-detective-madappgang

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers understand implementation details, data flow, and usage patterns using AST callers/callees analysis.

Core Features & Use Cases

Find Implementation: locate where a function is defined
Trace Data Flow: follow callee chains to understand data movement
Find All Usages: enumerate all function usages (callers)
Impact Analysis: assess ripple effects before changing code

Quick Start

claudemem --nologo symbol processPayment --raw; claudemem --nologo context processPayment --raw

Frequently Asked Questions about developer-detective

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

FAQPage Schema

How do I trace data flow through function calls in my codebase?▼

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.

How do I find all places where a function is being called?▼

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.

Can I assess the ripple effect before changing a function implementation?▼

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.

What setup do I need to use AST-based code analysis for implementation investigation?▼

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.

How do I locate where a specific function is defined in my codebase?▼

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.

Can I audit which external functions my code depends on?▼

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.