Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.
Coding
93 Stars
10 Forks
Updated Nov 26, 2025, 11:09 PM
Why Use This
This skill provides specialized capabilities for korallis's codebase.
Use Cases
Developing new features in the korallis repository
Refactoring existing code to follow korallis standards
Understanding and working with korallis's codebase structure
---
name: root-cause-tracing
description: Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.
---
# Root Cause Tracing - Debugging Deep Errors
## When to use this skill
- Debugging complex, multi-layered issues
- Tracing errors back through call stacks
- Investigating data corruption sources
- Following execution paths through systems
- Identifying where invalid data originates
- Finding root causes of cascading failures
- Debugging integration issues
- Tracing state changes backward
- Investigating intermittent bugs
- Following data flow through transformations
- Identifying the first point of failure
- Debugging asynchronous or distributed systems
## When to use this skill
- Tracing bugs backward through call stacks.
- When working on related tasks or features
- During development that requires this expertise
**Use when**: Tracing bugs backward through call stacks.
## Process
1. Reproduce issue reliably
2. Add instrumentation
3. Trace backwards
4. Find original trigger
5. Fix root cause
## Resources
- [Debugging Guide](https://jvns.ca/)
