skills.rest
mrkhachaturov
mrkhachaturovCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide engineers through phased root-cause investigation and evidence-based debugging.

Updated Mar 26, 2026
Search Tags:#debugging#investigation#defense-in-depth#evidence-based#root-cause-analysis#phased-workflow#askuserquestion
One-click install
npx skills add https://github.com/mrkhachaturov/rkstack --skill systematic-debugging-mrkhachaturov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/mrkhachaturov/rkstack/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/mrkhachaturov/rkstack --skill systematic-debugging-mrkhachaturov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, phased approach to diagnosing and fixing bugs, ensuring root-cause investigation is performed before proposing changes.

Core Features & Use Cases

  • Structured, phase-driven debugging workflows that guide discovery, evidence gathering, and hypothesis testing.
  • Defense-in-depth mindset: add validation and instrumentation across multiple layers to prevent regressions.
  • Applicable to any bug, test failure, or unexpected behavior across languages and stacks, from small scripts to large applications.

Quick Start

Start a guided debugging session by following the five-phase workflow to locate root causes and verify fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I perform root-cause analysis for a software defect instead of just patching symptoms?▼

Root-cause analysis for a software defect requires a phased debugging workflow that enforces evidence gathering and hypothesis testing before proposing fixes. This approach prevents fixes that address symptoms rather than underlying causes.

What is the best way to structure a debugging workflow for unexpected behavior across large codebases?▼

A structured debugging workflow for unexpected behavior uses a phase-driven process guiding discovery, evidence gathering, and hypothesis testing. It applies across languages and stacks from small scripts to large applications.

How does a defense-in-depth mindset help prevent regressions when fixing bugs?▼

A defense-in-depth mindset prevents regressions by adding validation and instrumentation across multiple layers during bug investigation. This ensures fixes are thoroughly verified and weaknesses are addressed comprehensively.

Can I use this evidence-based debugging approach for test failures in any programming language?▼

Yes, evidence-based debugging for test failures is applicable to any bug or unexpected behavior across languages and stacks. The workflow enforces documentation and prompts regardless of the specific technology used.

When should I use a phased investigation workflow rather than directly patching a bug?▼

A phased investigation workflow is necessary whenever you face a bug, test failure, or unexpected behavior and need to ensure root-cause investigation is performed before proposing changes, avoiding superficial symptom patches.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
elianivaelianiva
203

root-cause-tracing

Trace errors backward through a call stack to their original trigger.

Community
Advanced
flutterflutter
2.8k

dart-fix-runtime-errors

Identify and resolve Dart static analysis errors and runtime exceptions.

Official
Intermediate
kevinnftkevinnft
13

node-inspect-debugger

Drive Node.js debugging via CDP to set breakpoints and inspect runtime state.

Community
Advanced