Enforce root-cause investigation before fixing bugs and test failures.
npx skills add https://github.com/ArcadeAI/dexa --skill debugging-arcadeai
Please help me install this Agent Skill. Skill: debugging Source: https://github.com/ArcadeAI/dexa/tree/main/.claude/skills/safeword-debugging Command: npx skills add https://github.com/ArcadeAI/dexa --skill debugging-arcadeai
Four-phase debugging framework that ensures root cause identification before fixes. Use when encountering bugs, test failures, unexpected behavior, or when previous fix attempts failed. It enforces investigative discipline (e.g., "debug this", "fix this error", "test is failing", "not working").
Start with Phase 1: Root Cause Investigation and proceed through Phases 2–4 as described. Document findings and confirm root cause before applying any fix.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging follows a four-phase process: investigate the error completely, analyze patterns across failures, form and test hypotheses against data flow, then verify the fix. This ensures you solve the underlying issue, not just symptoms.
Repeated failed fixes signal you're treating symptoms. Return to phase one: read error messages completely, reproduce the failure consistently, trace data flow through affected components, and compare differences between working and broken states before attempting another fix.
Yes. The four-phase framework applies to bugs, test failures, unexpected behavior, and emergency scenarios across multi-component systems. It enforces investigative discipline regardless of failure type, ensuring durable resolutions under time pressure.
Fixing symptoms first masks underlying problems and leads to repeated failures. Systematic root-cause investigation—reading error messages, reproducing consistently, tracing data flow, and testing hypotheses—identifies what actually broke and prevents the bug from recurring.
Trace data flow through all affected components while comparing differences between working and broken states. This phase-based approach isolates which component introduced the failure and reveals how errors propagate, preventing incomplete fixes in distributed systems.
jk278Diagnose software bugs from stack traces and error logs.
skylarsaboFix confirmed bugs at root cause with evidence and regression guards.
Himanshu040604Integrate Sentry SDK for error tracking and performance monitoring in PHP applications.
CANTAGESTUDIODiagnose software defects through a four-phase root-cause investigation framework.
