skills.rest
seanGSISG
seanGSISGCOMMUNITY
Explore all skills by this author →
GitHub

root-cause-tracing

Trace call stacks backward to identify original error triggers.

3|Updated Nov 19, 2025
Search Tags:#debugging#root cause#troubleshooting#bug fix#stack trace#tracing#instrumentation
One-click install
npx skills add https://github.com/seanGSISG/crispy-claude --skill root-cause-tracing-seangsisg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: root-cause-tracing
Source: https://github.com/seanGSISG/crispy-claude/tree/main/.claude/skills/root-cause-tracing
Command: npx skills add https://github.com/seanGSISG/crispy-claude --skill root-cause-tracing-seangsisg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Bugs often manifest deep in the call stack, leading developers to fix symptoms rather than the original trigger, resulting in recurring issues. This skill provides a systematic method to trace bugs backward to their true source.

Core Features & Use Cases

  • Backward Tracing: Guides through identifying the immediate cause, then tracing up the call stack to find where invalid data or incorrect behavior originated.
  • Instrumentation: Recommends adding diagnostic logging with stack traces before problematic operations to capture crucial context.
  • Polluter Identification: Provides a bisection script (find-polluter.sh) to pinpoint which test or code introduces unwanted files or state.

Quick Start

Use the root-cause-tracing skill to investigate why 'git init' is failing in the wrong directory during the 'project-setup' test.

Frequently Asked Questions about root-cause-tracing

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

FAQPage Schema
How do I trace a bug back to its root cause when the stack trace is long?▼

Root-cause tracing guides you backward through the call stack to identify where invalid data or incorrect behavior originated, rather than fixing only the symptom. Trace from the error's immediate cause upward through each layer until you locate the true trigger.

What's the best way to identify which test is polluting state in my codebase?▼

Use instrumentation and bisection to pinpoint the source. The bisection script (`find-polluter.sh`) systematically narrows down which test or code introduces unwanted files or state changes that cause downstream failures.

How do I add instrumentation to capture context before errors occur?▼

Insert diagnostic logging with stack traces at layer boundaries and before problematic operations. This captures crucial state and execution flow, making it easier to trace invalid data or misconfigurations back to their origin.

When should I use root-cause analysis instead of quick symptom fixes?▼

Use root-cause tracing when bugs recur, errors manifest deep in execution, or you suspect the visible failure masks a deeper problem like test pollution, invalid data, or misconfiguration introduced elsewhere.

Can root-cause tracing help with misconfigurations and invalid data issues?▼

Yes. Root-cause tracing systematically traces backward to identify where misconfigurations were set or invalid data entered the system, addressing the original trigger rather than downstream symptoms.

Do I need to modify my existing test suite to use polluter identification?▼

No. The polluter identification approach uses a separate bisection script (`find-polluter.sh`) that runs alongside your tests to detect which test or code introduces unwanted state without requiring test modifications.

Related Skills

Explore More Software Engineering Skills→
aaaa47080aaaa47080
4

root-cause-tracing

Trace issues backward through the call stack to identify root causes.

Community
Advanced
TumeloRamaphosaTumeloRamaphosa

gstack-openclaw-investigate

Convert reported symptoms and stack traces into validated root-cause investigations.

Community
Advanced
Khoatran1999Khoatran1999

Root Cause Tracing

Trace bugs backward through call stacks to locate original triggers.

Community
Advanced
xebiaxebia

root-cause-tracing

Trace errors backward through the call stack to identify root causes.

Official
Advanced