Root Cause Tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

43 stars 13 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lifangda/claude-plugins

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lifangda/claude-plugins --skill root-cause-tracing
Manual install
git clone --depth 1 https://github.com/lifangda/claude-plugins.git /tmp/claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/claude-plugins/cli-tool/skills-library/problem-solving/root-cause-tracing ~/.claude/skills/root-cause-tracing

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Root Cause Tracing

## Overview

Bugs often manifest deep in the call stack (git init in wrong directory, file created in wrong location, database opened with wrong path). Your instinct is to fix where the error appears, but that's treating a symptom.

**Core principle:** Trace backward through the call chain until you find the original trigger, then fix at the source.

## When to Use

```dot
digraph when_to_use {
    "Bug appears deep in stack?" [shape=diamond];
    "Can trace backwards?" [shape=diamond];
    "Fix at symptom point" [shape=box];
    "Trace to original trigger" [shape=box];
    "BETTER: Also add defense-in-depth" [shape=box];

    "Bug appears deep in stack?" -> "Can trace backwards?" [label="yes"];
    "Can trace backwards?" -> "Trace to original trigger" [label="yes"];
    "Can trace backwards?" -> "Fix at symptom point" [label="no - dead end"];
    "Trace to original trigger" -> "BETTER: Also add defense-in-depth";
}
```

**Use when:**
- Error happens deep in execution (not at entry point)
- Stack trace shows long call chain
- Unclear where invalid data originated
- Need to find which test/code triggers the problem

## The Tracing Process

### 1. Observe the Symptom
```
Error: git init failed in /Users/jesse/project/packages/core
```

### 2. Find Immediate Cause
**What code directly causes this?**
```typescript
await execFileAsync('git', ['init'], { cwd: projectDir });
```

### 3. Ask: What Called This?
Read the full skill on GitHub

Details

Skill name
root-cause-tracing
Path
cli-tool/skills-library/problem-solving/root-cause-tracing/SKILL.md
License
MIT
Repo updated
29 October 2025

FAQ

What does the Root Cause Tracing skill do?

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

How do I install the Root Cause Tracing skill?

Claude Code plugin: /plugin marketplace add lifangda/claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Root Cause Tracing popular?

It lives in lifangda/claude-plugins, which has 43 GitHub stars and 13 forks.

Related skills

Test Driven Development

43

lifangda/claude-plugins

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

Software Development13

Video Downloader

43

lifangda/claude-plugins

Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.

Images, Video & Audio13

Aeon

43

lifangda/claude-plugins

Time series machine learning toolkit for classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use this skill when working with temporal data, performing time series analysis, building predictive models on sequential data, or implementing workflows that involve distance metrics (DTW), transformations (ROCKET, Catch22), or deep learning for time series. Applicable for tasks like ECG classification, stock price forecasting, sensor anomaly detection, or activity recognition from wearable devices.

Learning & Education13

Run

40

ArogyaReddy/alirezarezvani-claude-skills

Run a single experiment iteration. Edit the target file, evaluate, keep or discard.

Other11

Matchms

43

lifangda/claude-plugins

Mass spectrometry analysis. Process mzML/MGF/MSP, spectral similarity (cosine, modified cosine), metadata harmonization, compound ID, for metabolomics and MS data processing.

Other13

Specrate

10

rickygao/specrate

Skill to manage specs and changes. Use this when working with specrate-managed documents.

OtherIn 1 list

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.