skills.rest
haryelramalho
haryelramalhoCOMMUNITY
Explore all skills by this author →
Website𝕏@haryel_devGitHub

systematic-debugging

Trace root causes of bugs before proposing fixes.

Updated May 28, 2026
Search Tags:#debugging#root cause#troubleshooting#verification#test failures#hypothesis testing#bug investigation
One-click install
npx skills add https://github.com/haryelramalho/skills --skill systematic-debugging-haryelramalho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/haryelramalho/skills/tree/main/skills/curated/systematic-debugging
Command: npx skills add https://github.com/haryelramalho/skills --skill systematic-debugging-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted time on guess-and-check fixes by forcing a root-cause-first debugging process for bugs, test failures, performance issues, and unexpected behavior.

Core Features & Use Cases

  • Structured investigation: Read errors carefully, reproduce consistently, and check recent changes before touching code.
  • Pattern-driven analysis: Compare against working examples, trace data flow, and identify what differs from the broken path.
  • Safe, minimal fixes: Form one hypothesis at a time, test the smallest change possible, and create a failing test before implementation.
  • Escalation guardrails: If repeated fixes fail, stop and question the architecture instead of piling on more patches.

Quick Start

Use the systematic-debugging skill to investigate this issue from root cause to verified fix before proposing any change.

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 test failures before attempting a fix?▼

Bug investigation requires reading errors carefully, reproducing consistently, checking recent changes, comparing against working patterns, testing one hypothesis at a time, and creating a failing test before implementing any fix.

What is the best way to troubleshoot production defects and performance regressions?▼

Troubleshooting production defects and performance regressions requires tracing data flow, comparing broken paths against working examples, and verifying the root cause through single-hypothesis testing before proposing a minimal fix.

Why do my repeated bug fixes keep failing to resolve the issue?▼

Repeated bug fixes fail when you patch symptoms instead of the root cause. Stop piling on patches, question the architecture, re-read the error carefully, and verify the true root cause through systematic hypothesis testing.

Can I use systematic debugging for build breakages and unexpected technical behavior?▼

Yes, systematic debugging applies to build breakages and unexpected technical behavior by enforcing error reading, consistent reproduction, change review, pattern comparison, and root-cause verification prior to implementation.

Related Skills

Explore More Software Engineering Skills→
blakeoxblakeox

debugger

Reproduce software failures and isolate the root cause from code or logs.

Community
Advanced
mazicimertmazicimert

tdd-bug-fix

Reproduce bugs with failing tests and guide a minimal TDD fix workflow.

Community
Advanced
2460124601

investigate

Perform root cause analysis on software failures and bugs.

Community
Advanced
hungthinh04hungthinh04

systematic-debugging

Identify root causes of software bugs through error analysis and hypothesis testing.

Community
Advanced