skills.rest
poz110
poz110COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose implementation failures through a structured hypothesis-driven debugging process.

4|1|Updated Apr 6, 2026
Search Tags:#code review#debugging#root cause analysis#issue resolution#structured debugging
One-click install
npx skills add https://github.com/poz110/claude-harness --skill systematic-debugging-poz110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/poz110/claude-harness/tree/main/plugins/claude-harness/skills/systematic-debugging
Command: npx skills add https://github.com/poz110/claude-harness --skill systematic-debugging-poz110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The systematic-debugging skill addresses the challenge of inefficient debugging practices, providing a structured methodology to diagnose and resolve implementation failures promptly.

Core Features & Use Cases

  • Structured Debugging Methodology: Offers a 5-step process to methodically uncover root causes of issues.
  • Minimize and Hypothesize: Helps reduce the problem to a minimal test case and formulates hypotheses for root causes.
  • Verify and Fix: Encourages thorough testing and minimal code changes to verify and resolve issues.
  • Common Root Cause Analysis: Provides quick diagnostics for common issues like TypeScript type errors and intermittent failures.
  • Use Case: For developers who need to debug build failures, runtime errors, or unexpected behavior in their codebase.

Quick Start

To initiate systematic debugging, execute the following command in your environment: /start-debugging "Identify the root cause of the build failure."

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a structured approach to debugging unexpected behavior and build failures?▼

Structured debugging is a 5-step methodology to methodically uncover root causes of issues. It helps developers minimize the problem to a minimal test case, formulate hypotheses, and verify fixes for unexpected behavior or build failures.

How do I find the root cause of a runtime error or test failure?▼

To find the root cause of a runtime error, reduce the problem to a minimal test case and formulate hypotheses for the root causes. You can initiate this by executing the /start-debugging command with a description of your implementation failure.

Can I use this structured debugging process for TypeScript type errors?▼

Yes, you can use this structured debugging process for TypeScript type errors. It provides quick diagnostics for common issues like TypeScript type errors and intermittent failures to help identify and resolve implementation failures promptly.

What is the best way to resolve implementation failures without introducing new bugs?▼

The best way to resolve implementation failures is by applying a hypothesis-driven debugging process that encourages thorough testing and minimal code changes. This verifies and resolves issues while preventing new bugs in your codebase.

Does this debugging methodology work for intermittent failures in my codebase?▼

Yes, this debugging methodology works for intermittent failures in your codebase. It provides quick diagnostics specifically targeting common issues like intermittent failures and TypeScript type errors to resolve implementation failures efficiently.

Related Skills

Explore More Software Engineering Skills→
jaydubya818jaydubya818

systematic-debugging

Investigate bugs through root cause analysis, hypothesis testing, and phased implementation.

Community
Intermediate
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
laurenj3250-debuglaurenj3250-debug

systematic-debugging

Identify root causes of software bugs through a four-phase investigation workflow.

Community
Basic