skills.rest
bgrober
bgroberCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide a four-phase process to identify and resolve root causes of technical issues.

1|Updated Jan 7, 2026
Search Tags:#testing#debugging#investigation#root cause#troubleshooting#bug fixing
One-click install
npx skills add https://github.com/bgrober/indie-stack --skill systematic-debugging-bgrober
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/bgrober/indie-stack/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/bgrober/indie-stack --skill systematic-debugging-bgrober

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring that the root cause of any technical issue is identified and fixed, rather than just addressing the immediate symptom.

Core Features & Use Cases

  • Structured Investigation: Guides users through a mandatory four-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to systematically uncover the origin of bugs.
  • Resists Pressure: Provides explicit rules and anti-patterns to prevent shortcuts, especially under time pressure or when a quick fix seems obvious.
  • Use Case: When a test fails or an unexpected behavior occurs, use this Skill to ensure you don't just add a quick workaround, but instead, thoroughly investigate and fix the underlying problem, saving hours of future debugging.

Quick Start

Use the systematic debugging skill to investigate any bug or test failure before proposing fixes.

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 bug instead of just fixing the symptom?▼

Systematic debugging requires following a mandatory four-phase process: Investigation, Pattern Analysis, Hypothesis, and Implementation. This structured approach ensures you verify the origin of unexpected behaviors before attempting any code changes.

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

The best way to troubleshoot test failures is to systematically investigate the evidence and analyze behavioral patterns before proposing fixes. This prevents quick workarounds and ensures the underlying problem is fully resolved.

How do I stop taking debugging shortcuts when under time pressure?▼

To stop taking debugging shortcuts under time pressure, use explicit rules and anti-patterns that enforce a thorough investigation phase. This structured methodology actively resists common rationalizations that lead to incomplete bug fixes.

When should I use a systematic debugging process for software issues?▼

You should use a systematic debugging process whenever a test fails or unexpected behavior occurs across the software development lifecycle. It is essential for preventing wasted time and avoiding the introduction of new bugs from quick fixes.

Related Skills

Explore More Software Engineering Skills→
ssimhanssimhan
1

debugging

Reproduce software defects and verify fixes with evidence-based workflows.

Community
Basic
mandersogitmandersogit

debugging

Debug Python code by reproducing issues, analyzing logs, and verifying fixes.

Community
Basic
williamzujkowskiwilliamzujkowski
6

NIST SP 800-53 Compliance Validator

Validate NIST SP 800-53 controls with evidence mapping across 20 families.

Community
Advanced
HumanBean17HumanBean17
8

systematic-debugging

Enforce a four-phase systematic debugging process for root cause resolution.

Community
Advanced