Debug Root Cause

Overview

Use this skill to move from symptom to confirmed root cause with minimal guesswork and auditable evidence.

Scope Boundaries

• Use this skill when the task matches the trigger condition described in description.
• Do not use this skill when the primary task falls outside this skill's domain.
• If available, prefer github-fix-ci when the primary symptom is a GitHub Actions check failure.
• If available, prefer git-bisect-debugging when the unresolved question is "which commit introduced the regression?"
• If available, prefer performance-profiling when profiler evidence and optimization prioritization are the main objective.
• If available, prefer security-incident-response for active compromise triage/containment/eradication.
• If available, prefer incident-postmortem when incident stabilization is complete and the task is retrospective analysis.

Shared References

• Strategy matrix:
  • references/debug-strategy-matrix.md