skills.rest
eng-vmessiah
eng-vmessiahCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Execute a four-phase debugging process for root cause analysis.

2|Updated Jun 14, 2026
Search Tags:#debugging#investigation#troubleshooting#problem-solving#root-cause
One-click install
npx skills add https://github.com/eng-vmessiah/project-development-skill --skill systematic-debugging-eng-vmessiah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/eng-vmessiah/project-development-skill/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/eng-vmessiah/project-development-skill --skill systematic-debugging-eng-vmessiah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of guess-and-check debugging, which often leads to wasted time, recurring issues, and the introduction of new bugs.

Core Features & Use Cases

  • Four-Phase Debugging: Follows a strict, scientific process of investigation, pattern analysis, hypothesis testing, and implementation.
  • Architectural Guardrails: Includes a specific rule to stop and re-evaluate architecture if three or more fix attempts fail.
  • Use Case: When a production service experiences intermittent failures, this skill guides the agent to gather logs, trace data flow, and isolate the failing component before applying a targeted, verified fix.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the current test failure in the authentication module.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I find the root cause of a production bug instead of guessing?▼

Root cause analysis replaces guess-and-check debugging with a four-phase process: systematic evidence gathering, pattern analysis, hypothesis testing, and verified implementation to isolate the actual defect before applying a targeted fix.

What is the best way to troubleshoot intermittent test failures?▼

Troubleshooting intermittent test failures requires gathering logs, tracing data flow, and isolating the failing component through structured hypothesis testing rather than random changes, verifying the exact failure point for a permanent resolution.

How do I stop recurring software defects after multiple fix attempts?▼

To stop recurring software defects, apply an architectural guardrail: if three or more fix attempts fail, halt patching and re-evaluate the system architecture, preventing compounding errors and identifying deeper structural flaws.

Can I use systematic debugging for performance regressions?▼

Yes, systematic debugging applies to performance regressions by executing a structured investigation process, guiding you to gather evidence, test hypotheses about bottlenecks, and implement verified fixes to resolve the regression.

When should I re-evaluate architecture during defect resolution?▼

You should re-evaluate architecture during defect resolution when three or more targeted fix attempts fail, triggering a stop to patching and forcing a higher-level pattern analysis to find structural root causes.

Related Skills

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

error-debugging-error-analysis

Analyze logs, stack traces, and failure patterns to diagnose application errors.

Community
Advanced
adolfoaranaes12adolfoaranaes12
2

fix-issue

Reproduce bugs, identify root causes, and validate minimal fixes with the full test suite.

Community
Advanced
AribSudiaAribSudia
2

arib-dev-debug

Systematize software debugging through hypothesis testing and root cause analysis.

Community
Advanced
robkamrobkam
12

qa-root-cause-remediation

Diagnose QA gate failures and implement root-cause fixes with rerun plans.

Community
Advanced