skills.rest
HaRu-LLC
HaRu-LLCCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of software failures through structured, evidence-driven debugging.

Updated Nov 21, 2025
Search Tags:#debugging#troubleshooting#systematic#quality-assurance#root-cause-analysis#hypothesis-testing
One-click install
npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill systematic-debugging-haru-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse/tree/main/.agent/skills/engineering/systematic-debugging
Command: npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill systematic-debugging-haru-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a disciplined, evidence-based approach to debugging that requires root-cause investigation before attempting fixes.

Core Features & Use Cases

  • Root-cause analysis: Systematically analyze errors, reproduce issues, review changes, and trace data flow across system layers.
  • Phase-driven workflow: Enforces four consecutive phases: root-cause investigation, pattern analysis, hypothesis testing, and implementation.
  • Guardrails & escalation: Ensures escalation after repeated failure and discourages quick fixes that may introduce new problems.
  • Use Case: When debugging a failing service after deployment, apply this skill to identify the root cause and implement a minimal, verifiable patch.

Quick Start

Begin with root-cause analysis to identify the underlying fault before implementing a fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and when do I need it for software troubleshooting?▼

Systematic debugging is an evidence-driven approach to identify the true root cause of failures in software systems before attempting fixes, essential for persistent or transient issues in production and staging environments.

How do I find the root cause of a failing service after deployment?▼

To find the root cause of a failing service, apply a structured debugging process: reproduce the issue, review recent changes, trace data flow across system layers, and test hypotheses before implementing a minimal patch.

Can I use this debugging approach for both code and configuration issues?▼

Yes, this debugging approach applies to failures across code, configurations, and data flows, ensuring root-cause investigation and pattern analysis are performed before any implementation changes.

What is the best way to prevent quick fixes from introducing new bugs during root-cause analysis?▼

The best way to prevent new bugs is using a phase-driven workflow with guardrails that enforces consecutive root-cause investigation, pattern analysis, hypothesis testing, and minimal implementation before applying changes.

When should I escalate a software issue during hypothesis testing?▼

You should escalate a software issue during hypothesis testing when repeated attempts to reproduce or resolve the fault fail, triggering the skill's built-in escalation guardrails to avoid compounding errors.

Related Skills

Explore More Software Engineering Skills→
knowz-ioknowz-io
1

knowzcode-telemetry

Correlate Sentry and App Insights telemetry to diagnose production errors.

Official
Intermediate
korwlik23korwlik23

bug-debugging

Analyze error messages, stack traces, and logs to identify root causes and implement verified fixes.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
fmflurryfmflurry
171

build-description-test-error-resolution-2

Guide structured root-cause analysis to resolve recurring error failures.

Community
Advanced