Does it work with event-driven architectures?

While it excels at static analysis of call chains, it notes that some dynamic callbacks or event-driven patterns may require additional manual verification.

Why are grep and find forbidden in this skill?

Debugger Detective prioritizes structural AST analysis over keyword searching to provide accurate call-graph relationships and context that simple text searches often miss.

Can it analyze impact across the entire codebase?

Yes, it uses the 'callers' and 'impact' commands to trace every function that depends on a specific symbol, helping prevent regressions.

What is claudemem v0.3.0?

Claudemem is the underlying tool this skill uses to parse code structures, allowing Claude to understand the relationships between symbols, functions, and classes.

Debugger Detective

Name: Debugger Detective
Author: tianzecn

bytianzecn

•

Developer Tools

Pinpoints software bugs and identifies root causes through advanced AST-based call chain analysis.

About

Debugger Detective is a specialized skill for Claude Code designed for deep codebase investigations and incident response. By leveraging claudemem AST analysis, it allows developers to trace execution paths backwards to find the source of errors or forwards to map the blast radius of a bug. It replaces manual searching with structured call-graph navigation, making it indispensable for resolving complex logic failures, state mutations, and regression analysis without relying on imprecise text searches like grep or find.

Key Features

Automated root cause identification via symbol context analysis
Blast radius analysis to identify code impacted by bugs or fixes
AST-driven call chain tracing to map function relationships
State mutation tracking to find where data integrity is lost
1 GitHub stars
Structured bug investigation reporting for incident documentation

Use Cases

Performing impact analysis before a refactor to see all affected callers
Identifying the flow of data through complex asynchronous or nested function calls
Tracing the origin of a null pointer exception or runtime error back to the source

About

Key Features

Automated root cause identification via symbol context analysis
Blast radius analysis to identify code impacted by bugs or fixes
AST-driven call chain tracing to map function relationships
State mutation tracking to find where data integrity is lost
1 GitHub stars
Structured bug investigation reporting for incident documentation

Use Cases

Performing impact analysis before a refactor to see all affected callers
Identifying the flow of data through complex asynchronous or nested function calls
Tracing the origin of a null pointer exception or runtime error back to the source