skills.rest
attentiondotnet
attentiondotnetCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose bugs through four-phase root-cause investigation with evidence gathering and regression verification.

Updated Mar 30, 2026
Search Tags:#testing#debugging#systematic#reproducibility#root-cause#phase-based
One-click install
npx skills add https://github.com/attentiondotnet/hermes-agent --skill systematic-debugging-attentiondotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/attentiondotnet/hermes-agent/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/attentiondotnet/hermes-agent --skill systematic-debugging-attentiondotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging reduces wasted time by enforcing a structured root-cause investigation before proposing fixes, ensuring problems are understood before changes are made.

Core Features & Use Cases

  • Four-phase workflow: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis & Testing, Phase 4 Implementation.
  • Built-in guardrails for evidence gathering, reproducibility, and regression-focused validation.
  • Use cases include: test failures, production bugs, and integration issues where symptoms are unclear or evolving.

Quick Start

Begin by reading the error, reproducing the issue consistently, tracing the data flow, and applying the four-phase process to identify the root cause before fixing.

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 transient test failure without guessing?▼

Root-cause debugging enforces a structured four-phase investigation to diagnose transient test failures, requiring evidence gathering and consistent reproduction before any fix is proposed.

What is the best way to debug production bugs when symptoms are unclear or evolving?▼

Systematic debugging applies a four-phase workflow—investigation, pattern analysis, hypothesis testing, and implementation—to resolve production bugs with unclear symptoms by enforcing evidence-based root-cause discovery.

How do I systematically debug integration issues step by step?▼

You systematically debug integration issues by reproducing the issue consistently, tracing data flow, and applying four phases: root cause investigation, pattern analysis, hypothesis testing, and controlled implementation with regression verification.

Does systematic debugging work for multi-step debugging scenarios involving complex data flow?▼

Yes, systematic debugging applies to any multi-step debugging scenario by enforcing evidence gathering, pattern analysis, hypothesis testing, and controlled implementation with regression-focused validation to ensure problems are understood before changes are made.

Why should I use a phase-based debugging approach instead of immediately patching code?▼

A phase-based debugging approach reduces wasted time by enforcing structured root-cause investigation before proposing fixes, ensuring problems are fully understood through evidence gathering and hypothesis testing before changes are made.

Can I use this debugging workflow for regression verification after implementing a fix?▼

Yes, the implementation phase includes built-in guardrails for regression-focused validation, ensuring that controlled fixes are verified against the original issue and do not introduce new defects.

Related Skills

Explore More Software Engineering Skills→
tutur3ututur3u
53

systematic-debugging

Enforce root-cause investigation before fixing software bugs.

Official
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
ryan-mtryan-mt
3

webapp-testing

Automates web app testing and debugging with Python and Playwright.

Community
Intermediate
Sir-chawakornSir-chawakorn
33

debugging

Guide systematic debugging to identify, isolate, and resolve software defects.

Community
Intermediate