Root Cause Tracing

Use when symptoms don't reveal the cause. Trace backward through call chains to find where problems originate. Follow: Observe symptom → Find immediate cause → Identify caller → Keep tracing → Locate trigger.

8 stars 3 forksOther Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Freddy-CHEN-ux/00_claude_skills

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 Freddy-CHEN-ux/00_claude_skills --skill root-cause-tracing
Manual install
git clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/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

## Core Principle

Symptoms appear downstream. Root causes live upstream. Trace backward through the call chain until you find the original trigger.

## When to Use This Skill

- Bug appears far from its source
- Symptoms don't reveal the cause
- Test failures that make no sense
- Data corruption or invalid state
- "How did this value get here?"
- Intermittent failures with no clear pattern
- Test pollution (one test affects another)

## The Iron Law

**NEVER STOP AT THE SYMPTOM. Trace backward until you find the ORIGINAL TRIGGER.**

Fixing symptoms is temporary. Fixing root causes is permanent.

## Why Root Cause Tracing?

**Benefits:**
✅ Finds actual cause, not just symptoms
✅ Prevents problem from recurring
✅ Reveals systemic issues
✅ Builds system understanding
✅ Fixes multiple symptoms at once

**Without root cause tracing:**
❌ Fix one symptom, three more appear
❌ Same bug keeps coming back
❌ Waste time on wrong solutions
❌ Never understand the real problem
❌ Accumulate technical debt

## The Backward Tracing Process

### Step 1: Observe the Symptom

```
🔍 OBSERVE Phase

Symptom: User profile page shows wrong user data

Specific observation:
- User A logs in
- Views profile page (/profile)
- Sees User B's name and email
- But sees own profile picture

Initial symptom recorded ✅
```

**What to capture:**
- Exact behavior observed
- Expected vs actual
- When it occurs
- Under what conditions
- Any error messages

### Step 2: Find Immediate Cause
Read the full skill on GitHub

Details

Skill name
root-cause-tracing
Path
skills/root-cause-tracing/SKILL.md
Repo updated
10 January 2026

FAQ

What does the Root Cause Tracing skill do?

Use when symptoms don't reveal the cause. Trace backward through call chains to find where problems originate. Follow: Observe symptom → Find immediate cause → Identify caller → Keep tracing → Locate trigger.

How do I install the Root Cause Tracing skill?

Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. 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 Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.

Related skills

Add Integration

8

Freddy-CHEN-ux/00_claude_skills

Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.

Software Development

AI Agents

8

Freddy-CHEN-ux/00_claude_skills

Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)

AI, LLMs & Agents

AI LLM

8

Freddy-CHEN-ux/00_claude_skills

Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.

AI, LLMs & Agents

Therapist Data Scientist

8

Freddy-CHEN-ux/00_claude_skills

Calculate Gottman SPAFF affect ratios and other therapeutic insights for relationship coaching data. Employee-facing tool for HIPAA-certified team members.

Other

Project Planner

8

Freddy-CHEN-ux/00_claude_skills

Use this skill when the user wants to plan a new project or feature implementation. This skill helps gather requirements through an iterative question-and-answer process, tracking decisions in a markdown file until a comprehensive specification is ready.

Other

Update Nexus

8

Freddy-CHEN-ux/00_claude_skills

Update Nexus system files from upstream repository. Load when user says "update nexus", "sync nexus", "get nexus updates", "check for updates", "upgrade nexus". Safely pulls system updates while protecting user data.

Other

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