skills.rest
samlaggz
samlaggzCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured root-cause debugging through evidence gathering and hypothesis testing.

Updated May 21, 2026
Search Tags:#debugging#troubleshooting#diagnostics#root-cause#software-engineering#data-flow
One-click install
npx skills add https://github.com/samlaggz/hermes-agent-sam --skill systematic-debugging-samlaggz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/samlaggz/hermes-agent-sam/tree/main/backup/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/samlaggz/hermes-agent-sam --skill systematic-debugging-samlaggz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and generate new issues. This approach ensures teams uncover root causes before applying patches, reducing rework and accelerating repair.

Core Features & Use Cases

  • Phase-based workflow (Phase 1–4) to systematically investigate, hypothesize, and verify fixes.
  • Evidence-driven debugging with data flow tracing, reproducibility checks, and controlled changes.
  • Collaboration-ready with delegation, testing, and safe rollback guidance for production scenarios.

Quick Start

Begin by following Phase 1 to gather evidence, reproduce the issue, and proceed through Phase 4 to implement a root-cause fix.

Frequently Asked Questions about systematic-debugging

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

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

Systematic root-cause debugging is a structured workflow to identify and resolve software bugs through data gathering, pattern analysis, hypothesis testing, and verified implementation. Use it for test failures, production bugs, performance problems, and integration issues to prevent random fixes.

How do I debug software issues using a phase-driven workflow?▼

Debug software issues by following a four-phase workflow: gather evidence and reproduce the issue in Phase 1, analyze patterns and data flow in Phase 2, test hypotheses in Phase 3, and implement verified fixes with regression safety in Phase 4.

Does this debugging approach work for production bugs and integration issues?▼

Yes, this debugging approach applies to production bugs and integration issues across any codebase. It includes safe rollback guidance, delegation, and testing protocols to ensure controlled changes and collaboration-ready investigation in production scenarios.

What's the best way to troubleshoot recurring bugs without introducing new issues?▼

The best way to troubleshoot recurring bugs without new issues is evidence-driven debugging with reproducibility checks, data flow tracing, and minimal changes. Applying controlled, verified fixes ensures root causes are resolved rather than patched.

Why do my random bug fixes keep generating new problems?▼

Random bug fixes generate new problems because they patch symptoms without uncovering root causes. A structured debugging workflow resolves the actual issue through evidence gathering and hypothesis testing, reducing rework and accelerating repair.

Can I standardize debugging practices across my engineering team?▼

Yes, you can standardize debugging practices using templates and integration guidance that enforce phase-driven analysis, evidence gathering, reproducibility, and regression safety, ensuring consistent root-cause investigation across the team.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
thomasslobodathomassloboda

incident-debugging

Identify and resolve incidents with a structured debugging workflow.

Community
Intermediate
TencentBlueKingTencentBlueKing
862

apm-trace-analysis

Analyze APM trace data to diagnose application issues and bottlenecks.

Official
Intermediate
kk20300113-pngkk20300113-png

investigate

Guide structured root-cause debugging for software errors and regressions.

Community
Advanced