Is this skill language-specific?

No, the core principles of call stack tracing, instrumentation, and multi-layer validation apply across all programming languages and environments.

What is defense-in-depth validation?

It is the practice of adding validation checks at every layer of the call chain discovered during tracing, ensuring that invalid state is caught as close to the source as possible in the future.

How does Root Cause Tracing differ from standard debugging?

While standard debugging often focuses on where an error occurs, this skill emphasizes tracing backward to the original trigger point to prevent the bug from recurring at different layers.

Can this skill help with flaky or failing tests?

Yes, it includes specialized methods like bisection scripts to identify 'polluter' tests that modify global state and cause subsequent, unrelated tests to fail.

Root Cause Tracing

Name: Root Cause Tracing
Author: nordeim

bynordeim

보안 및 테스팅

Systematically traces bugs backward through call stacks to identify and resolve original triggers rather than treating symptoms.

소개

This skill empowers Claude to perform deep, systematic debugging by tracing errors backward through the execution chain. Instead of simply fixing where an error appears, it guides the AI to identify the original trigger point in the call stack, implement defense-in-depth validation at multiple layers, and use specialized techniques like instrumentation and test-pollution bisection. It is particularly effective for complex software architectures where errors manifest deep in execution, far from the source of invalid data or state.

주요 기능

Systematic backward call stack tracing logic
Bisection-based identification of test environment pollution
Root cause vs. symptom differentiation
0 GitHub stars
Custom instrumentation and stack trace logging patterns
Defense-in-depth validation layer implementation

사용 사례

Resolving complex bugs where errors occur in dependencies due to upstream misconfiguration
Locating specific tests causing state pollution in large test suites
Identifying the source of invalid data passed through multiple abstraction layers

소개

주요 기능

Systematic backward call stack tracing logic
Bisection-based identification of test environment pollution
Root cause vs. symptom differentiation
0 GitHub stars
Custom instrumentation and stack trace logging patterns
Defense-in-depth validation layer implementation

사용 사례

Resolving complex bugs where errors occur in dependencies due to upstream misconfiguration
Locating specific tests causing state pollution in large test suites
Identifying the source of invalid data passed through multiple abstraction layers