What problem does it solve?
Bugs often manifest deep in the call stack, leading to the temptation to fix symptoms rather than the original trigger, resulting in recurring issues and wasted debugging time.
Core Features & Use Cases
- Backward Traceability: Systematically traces bugs backward through the call stack to identify the original source of invalid data or incorrect behavior.
- Instrumentation Guidance: Provides patterns for adding diagnostic logging and stack traces to gather crucial evidence.
- Polluter Identification: Includes a script to bisect and find which test or code introduces unwanted state or files, streamlining debugging.
- Use Case: When an error occurs deep within a complex system, this skill guides you to trace back through the execution flow, pinpointing the exact line of code where the problem originates, rather than just patching the visible symptom.
Quick Start
I'm seeing an error about 'file not found' deep in the logs. Use the root-cause-tracing skill to help me find where the incorrect file path is being generated.