skills.rest
tianzecn
tianzecnCOMMUNITY
Explore all skills by this author →
GitHub

debugger-detective

Diagnose bug root causes via AST-based call-chain analysis with claudemem v0.3.0.

2|Updated Dec 25, 2025
Search Tags:#debugging#trace#AST#root-cause#incident#call-chain
One-click install
npx skills add https://github.com/tianzecn/myclaudecode --skill debugger-detective-tianzecn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugger-detective
Source: https://github.com/tianzecn/myclaudecode/tree/main/plugins/code-analysis/skills/debugger-detective
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill debugger-detective-tianzecn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex codebases requires locating error origins, tracing call chains, and understanding state mutations. This skill provides a focused, AST-powered approach to root-cause analysis using claudemem v0.3.0, with strict guidance to avoid non-AST search methods.

Core Features & Use Cases

  • AST-based analysis: Use claudemem --nologo context, symbol, callers, and callees for full call chains.
  • Full call chain visibility: See both upstream callers and downstream callees for impact analysis.
  • Blast radius analysis: Optional impact checks to identify affected modules.
  • Error origin hunting: Map errors to source definitions and throwing sites.
  • State mutation tracking: Find where and how state changes occur.
  • Incident documentation: Record findings and suggested fixes.

Quick Start

Run claudemem --nologo context <function> --raw to get the full call context, then use claudemem --nologo impact <buggyFunction> --raw to analyze the blast radius.

Frequently Asked Questions about debugger-detective

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

FAQPage Schema
How do I trace the root cause of an error in my codebase using AST analysis?▼

Root-cause analysis with AST-driven tracing uses claudemem to map call chains from error sites back to their origin. Run claudemem --nologo context <function> --raw to inspect the full call stack, then claudemem --nologo impact <buggyFunction> --raw to identify affected modules and trace where the bug originates.

What is AST-based call-chain analysis and how does it help with debugging?▼

AST-based call-chain analysis parses your code's abstract syntax tree to reveal both upstream callers and downstream callees around a bug. This provides full visibility into how functions interact, making it easier to locate error origins and understand the blast radius without text-search limitations.

Can I use this debugging approach when grep and find commands are restricted?▼

Yes. This skill enforces claudemem v0.3.0 context tools instead of GREP, FIND, or GLOB searches. The claudemem --nologo commands provide static AST analysis that works within restricted environments while delivering structured call-chain and blast-radius results.

How do I identify which parts of my codebase are affected by a bug I found?▼

Use claudemem --nologo impact <buggyFunction> --raw to perform blast-radius analysis. This traces all downstream callees and upstream callers connected to the buggy function, showing you the scope of affected modules and state mutations across your system.

What preparation do I need before analyzing a bug with AST tracing?▼

You need claudemem v0.3.0 installed and access to your codebase's symbol definitions. The skill requires that GREP, FIND, and GLOB tools be unavailable or forbidden; claudemem's static AST analysis replaces those search methods to enforce full call-chain visibility.

Related Skills

Explore More Software Engineering Skills→
tianzecntianzecn
2

architect-detective

Analyze software architecture using AST structural analysis to map layers and dependencies.

Community
Advanced
heaptracetechnologyheaptracetechnology
13

incident-response

Guide incident response with severity triage, blast radius scoping, and blameless postmortems.

Community
Advanced
phuhao00phuhao00
12

code-analyst-agent

Analyze source code to identify symbols, call graphs, and architectural patterns.

Community
Intermediate
flosrnflosrn

Root Cause Tracing

Trace bugs backward through call stacks to identify original trigger points.

Community
Advanced