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];
More from glennguilloux/context-engineering-kit
setup-serena-mcp
Guide for setup Serena MCP server for semantic code retrieval and editing capabilities
9tree-of-thoughts
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with multi-agent evaluation
6write-concisely
Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
4setup-arxiv-mcp
Guide for setup arXiv paper search MCP server using Docker MCP
4analyse
Auto-selects best Kaizen method (Gemba Walk, Value Stream, or Muda) for target
3setup-code-formating
Sets up code formatting rules and style guidelines in CLAUDE.md
3