
When you're staring at an error five layers deep in the call stack, your first instinct is to patch it where it breaks. This skill teaches you to resist that urge and trace backward to find the actual source. It's designed for those frustrating bugs where git init runs in the wrong directory or a file gets created somewhere unexpected because bad data got passed down through multiple function calls. Part of a larger systematic debugging workflow, this focuses specifically on Phase 1 root cause investigation. The approach is simple but disciplined: follow the chain back until you find where things first went wrong, then fix it there instead of bandaging symptoms downstream.
$ npx -y skills add bobmatnyc/claude-mpm-skills --skill 'Root Cause Tracing' --agent claude-codeInstalls into .claude/skills of the current project.
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 skill is a specialized technique within the systematic-debugging workflow, typically applied during Phase 1 (Root Cause Investigation) when dealing with deep call stacks.
Use root-cause-tracing when:
Relationship with systematic-debugging:
NEVER FIX JUST WHERE THE ERROR APPEARS
ALWAYS TRACE BACK TO FIND THE ORIGINAL TRIGGER
Sponsors