skills.rest
arvidfcjarfalla-prog
arvidfcjarfalla-progCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose root causes of software, test, and build failures.

Updated Mar 12, 2026
Search Tags:#debugging#root-cause-analysis#hypothesis-testing#phase-workflow#evidence-gathering#production-stability
One-click install
npx skills add https://github.com/arvidfcjarfalla-prog/atlas --skill systematic-debugging-arvidfcjarfalla-prog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/arvidfcjarfalla-prog/atlas/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/arvidfcjarfalla-prog/atlas --skill systematic-debugging-arvidfcjarfalla-prog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured debugging discipline that forces root cause analysis before attempting any fix, reducing symptom fixes and wasted time.

Core Features & Use Cases

  • Four-phase debugging workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation.
  • Evidence gathering, traceability, and guardrails to prevent regressive changes.
  • Use case: when something fails, breaks, or behaves unexpectedly, follow the phases to identify the true cause and validate fixes.

Quick Start

Follow the four-phase debugging process to identify and fix the root cause before attempting any fixes.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a systematic debugging workflow for identifying root causes?▼

Systematic debugging is a strict four-phase workflow that enforces evidence gathering, pattern analysis, and hypothesis testing to identify root causes before applying fixes.

How do I debug build errors and test failures without applying symptom fixes?▼

To debug build errors and test failures, follow the four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement guarded changes to avoid symptom fixes.

Can I use this structured root-cause-analysis process for production stability issues?▼

Yes, you can use this root-cause-analysis process for production stability issues, as it applies across software, pipelines, UI, and integrations to safely remediate failures.

Does this debugging method work for diagnosing incorrect AI outputs?▼

Yes, this debugging method works for diagnosing incorrect AI outputs by applying hypothesis testing and pattern analysis to identify the true cause of the unexpected behavior.

What's the best way to fix unexpected software failures without causing regressions?▼

The best way to fix unexpected software failures without regressions is to use implementation guardrails during the final phase, ensuring changes are validated against gathered evidence.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

error-detective

Extract error patterns from logs and stack traces to identify root causes.

Community
Advanced
heyJordanParkerheyJordanParker
20

debug

Trace root causes of software bugs through a four-phase debugging process.

Community
Intermediate
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced
abranjithabranjith

fix

Diagnose software bugs, apply minimal fixes, and add regression tests.

Community
Advanced