Root Cause Tracing is a Quality skill for Claude Code, published by microsoft in FluidFramework.
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
Root Cause Tracing is cataloged under Quality on DirSkills. Root Cause Tracing comes from a repository tagged collaboration, crdt, datastructure, distributed and fluid.
Documentation
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.
This is the opening of the README. Read the full README on GitHub.
Root Cause Tracing is one of 31 skills that DirSkills catalogs from microsoft/FluidFramework, the repository it ships in. Its siblings there include API Changes Review, Brainstorming and Building UI/UX. Each one is a separate skill with its own page in this directory, installs the same way Root Cause Tracing does, and is maintained by microsoft in that same repository. The rest of the collection is listed on the microsoft/FluidFramework page.
Root Cause Tracing ranks #300 by stars among the 1897 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Root Cause Tracing against them. Open each page to compare what they document and how they install.
Root Cause Tracing is one of 31 skills cataloged on DirSkills from microsoft/FluidFramework.
Root Cause Tracing is one of 1897 Quality skills cataloged on DirSkills, ranked #300 by stars among them.