skills.rest
lshtram
lshtramCOMMUNITY
Explore all skills by this author →
GitHub

Systematic Debugging

Guide software debugging through observation, instrumentation, hypothesis testing, and fix verification.

1|Updated Mar 2, 2026
Search Tags:#testing#debugging#troubleshooting#root cause analysis#logging#bug fixing
One-click install
npx skills add https://github.com/lshtram/accordo --skill systematic-debugging-lshtram
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/lshtram/accordo/tree/main/skills/debugging
Command: npx skills add https://github.com/lshtram/accordo --skill systematic-debugging-lshtram

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, repeatable process to diagnose and fix bugs efficiently, ensuring you address the root cause rather than just the symptoms.

Core Features & Use Cases

  • Phased Approach: Guides you through observation, instrumentation, hypothesizing, verification, and fixing.
  • Targeted Logging: Offers best practices for adding effective instrumentation to expose hidden state.
  • Hypothesis Testing: Encourages forming and testing specific, ranked hypotheses to pinpoint the exact cause.
  • Use Case: When a critical test fails unexpectedly, load this Skill to systematically gather information, add necessary logs, form hypotheses about the failure, and verify the root cause before implementing a fix.

Quick Start

Use the debugging skill to follow the five-phase rule when a test fails.

Frequently Asked Questions about Systematic Debugging

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

FAQPage Schema
What is the best way to systematically debug a failing test instead of just fixing symptoms?▼

Systematic debugging provides a structured workflow to efficiently fix bugs by guiding you through observation, targeted logging, hypothesis testing, and minimal fix verification to ensure root cause resolution.

How do I add targeted logging to expose hidden state during troubleshooting?▼

Targeted logging involves adding specific instrumentation to your code to expose hidden application state. This systematic debugging approach helps gather necessary information and verify hypotheses about unexpected failures before implementing a fix.

Can I use hypothesis testing to find the root cause of a software bug?▼

Yes, hypothesis testing encourages forming and testing specific, ranked hypotheses to pinpoint the exact cause of a bug. This structured approach replaces guesswork with systematic verification to ensure accurate root cause analysis.

Does this systematic debugging approach require any specific testing frameworks or dependencies?▼

No, this debugging approach has no dependencies and provides a framework-agnostic workflow. It supports developers in complex debugging scenarios by offering a structured five-phase process and anti-pattern avoidance strategies.

When should I follow the five-phase debugging workflow for software issues?▼

You should follow the five-phase debugging workflow whenever a critical test fails unexpectedly or you face complex software issues. It helps you systematically gather information, form hypotheses, and verify the root cause before applying a minimal fix.

Related Skills

Explore More Software Engineering Skills→
Sh3rd3nSh3rd3n
3

debug

Guide systematic four-phase debugging with adaptive techniques for issue types.

Community
Advanced
berlysiaberlysia
9

bugfix

Reproduce bugs, write failing tests, and verify minimal fixes via TDD.

Community
Advanced
lv7devlv7dev

Root Cause Tracing

Trace call stacks backward to identify original bug triggers.

Community
Advanced
gofhirgofhir
2

go-code-review

Analyze Go source code with golangci-lint and go vet for bugs and race conditions.

Official
Intermediate