skills.rest
createdbysalt
createdbysaltCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose root causes of bugs through four-phase systematic debugging.

Updated Jan 22, 2026
Search Tags:#debugging#diagnostics#traceability#reproducibility#root-cause-analysis#pattern-analysis
One-click install
npx skills add https://github.com/createdbysalt/nextjs-starter-template --skill systematic-debugging-createdbysalt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/createdbysalt/nextjs-starter-template/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/createdbysalt/nextjs-starter-template --skill systematic-debugging-createdbysalt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined approach to debugging that prevents patching symptoms without identifying root causes.

Core Features & Use Cases

  • Root Cause Investigation: Reproduce, observe, and trace the origin of failures before attempting fixes.
  • Pattern Analysis: Compare working and broken implementations to identify behavioral differences.
  • Hypothesis and Testing: Formulate testable hypotheses and execute minimal tests to confirm or refute them.
  • Implementation: Implement fixes strictly after confirming the root cause, then verify with full test coverage.
  • Red Flags & Validation: Use the included checklists to stop unsafe patches and escalate when architectural issues are detected.

Quick Start

Apply the four-phase debugging framework to a failing scenario: reproduce the issue, collect diagnostic evidence (logs, traces), map the call chain, form a hypothesis, run a minimal test, and implement a root-cause fix followed by verification.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is root-cause debugging and when should I use it?▼

Root-cause debugging identifies the actual origin of failures before applying fixes. Use it for runtime errors, flaky tests, and regression investigations to prevent patching symptoms without solving the underlying problem.

How do I debug flaky tests systematically?▼

Debug flaky tests by reproducing the issue, collecting diagnostic evidence like logs and traces, mapping the call chain, forming a hypothesis, running a minimal test, and implementing a fix followed by verification.

What's the best way to investigate regression failures without patching symptoms?▼

Investigate regression failures by enforcing a no-fix-until-root-cause policy: reproduce the issue, compare working and broken implementations to identify behavioral differences, and require diagnostic evidence throughout the process.

How do I form testable hypotheses during root-cause analysis?▼

Formulate testable hypotheses during root-cause analysis by comparing working and broken implementations to identify behavioral differences, then execute minimal tests to confirm or refute each hypothesis before implementation.

When should I escalate a bug fix during systematic debugging?▼

Escalate a bug fix during systematic debugging when architectural issues are detected during pattern analysis or implementation, using the included validation checklists to stop unsafe patches and trigger escalation.

Related Skills

Explore More Software Engineering Skills→
tiagofurtiagofur

Bug Investigation

Investigate software defects and identify root causes across codebases.

Community
Intermediate
bhianerdbhianerd
1

investigate

Guide root-cause debugging with evidence collection and hypothesis validation.

Community
Advanced
Amar1404Amar1404
1

compare-datasets

Compare metrics and patterns across datasets to identify similarities and differences.

Community
Advanced
leonanpereirapintoleonanpereirapinto
1

no-workarounds

Enforce root-cause fixes by detecting and rejecting workaround patterns in code.

Community
Advanced