root-cause-tracing
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
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"];
More from enuno/claude-command-and-control
case-analyzer
Analyzes legal case facts and identifies viable legal theories, causes of action, and evidentiary requirements. Use when conducting case intake, strategy development, or initial legal analysis.
26architect-role-skill
|
16gitbook
GitBook documentation platform - creating docs, publishing sites, Git sync, API references, and collaboration
14file-categorization
Reusable logic for categorizing files as Command, Agent, Skill, or Documentation based on structure and content analysis
13builder-role-skill
|
12google-structured-data
Google Search structured data implementation - Schema.org markup for rich results, JSON-LD templates, JavaScript generation, and SEO best practices
12