debugging

Diagnose software defects through root cause analysis and verification protocols.

1|Updated Feb 17, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #validation #bug fixing #verification

Ready to run

npx skills add https://github.com/chef0111/physthink --skill debugging-chef0111

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/chef0111/physthink/tree/main/.agents/skills/debugging
Command: npx skills add https://github.com/chef0111/physthink --skill debugging-chef0111

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides structured methodologies to systematically find and fix bugs, preventing the common pitfalls of guesswork and symptom-fixing that lead to wasted time and recurring issues.

Core Features & Use Cases

Root Cause Analysis: Ensures you identify the fundamental reason for a bug, not just its symptoms.
Defense-in-Depth Validation: Builds robust checks at multiple layers to make bugs structurally impossible.
Verification Protocols: Guarantees fixes are confirmed before claiming completion.
Use Case: When a critical bug appears in production, this Skill guides you through a rigorous process to find the true origin, implement a lasting fix, and verify its effectiveness, minimizing downtime and future occurrences.

Quick Start

Use the debugging skill to systematically investigate the root cause of a test failure.

Frequently Asked Questions about debugging

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

FAQPage Schema

What is the best way to find the root cause of a production bug instead of just fixing symptoms?▼

Root cause analysis identifies the fundamental origin of a production bug rather than its symptoms. It enforces a structured, multi-phase investigation to prevent superficial symptom-fixing and ensures lasting software defect resolution.

How do I systematically debug unexpected software behavior and test failures?▼

To systematically debug unexpected behavior and test failures, apply a structured debugging framework. This methodology guides you through rigorous phases of investigation, root cause identification, and resolution to prevent wasted time on guesswork.

How does defense-in-depth validation make bugs structurally impossible?▼

Defense-in-depth validation makes bugs structurally impossible by building robust checks at multiple layers of the software. This systematic approach catches defects early and enforces thoroughness throughout the investigation and resolution process.

How can I verify a bug fix before claiming the debugging process is complete?▼

Verification protocols guarantee a bug fix is confirmed before claiming completion. By enforcing strict methodological adherence, these protocols ensure the fix is thoroughly tested and verified against the original unexpected behavior.

When do I need a systematic debugging framework for troubleshooting software defects?▼

You need a systematic debugging framework when a critical bug appears in production or when facing persistent test failures. It provides a rigorous process to find the true origin, implement a lasting fix, and minimize downtime.