debugging

Diagnose software bugs using a structured scientific debugging method.

39|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/hffmnnj/opencode-goopspec --skill debugging-hffmnnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/debugging
Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill debugging-hffmnnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you through a structured debugging process to quickly identify and fix issues with scientific rigor.

Core Features & Use Cases

  • Structured Debugging Workflow: Follow Observe → Hypothesize → Experiment → Analyze to isolate root causes.
  • Practical Strategies: Binary search, print/log tracing, rubber-duck explanation, minimal reproduction, and Git bisect to pinpoint faults.
  • Real-World Scenarios: Debug software defects in multi-language stacks, track down intermittent issues, and verify fixes before deploying.

Quick Start

Describe a bug you are facing and provide a minimal reproducible example to start the debugging process.

Frequently Asked Questions about debugging

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

FAQPage Schema
How do I systematically diagnose and fix bugs in my code?

Follow a structured debugging workflow: observe the bug's behavior, hypothesize its root cause, experiment with targeted tests, and analyze results. This scientific method isolates faults faster than trial-and-error across multiple languages and environments.

What's the best way to reproduce a bug so I can fix it?

Create a minimal reproduction case that triggers the bug consistently with the fewest steps and dependencies. Document the exact environment, inputs, and expected versus actual outputs to enable systematic diagnosis.

How do I use git bisect to find which commit introduced a bug?

Git bisect performs binary search across your commit history to pinpoint the exact change that broke functionality. Mark commits as good or bad, and bisect narrows the culprit in logarithmic steps.

What debugging techniques work for intermittent or hard-to-reproduce issues?

Combine log tracing to track execution flow, rubber-duck explanation to reason through logic aloud, and binary search to isolate which component or condition triggers the fault intermittently.

Can I debug code written in multiple programming languages with one approach?

Yes, the structured observe-hypothesize-experiment-analyze method applies across all languages and environments. Core techniques like binary search, log tracing, and minimal reproduction are language-agnostic.

How do I verify a bug fix before deploying it?

Test your fix against the original minimal reproduction case and edge cases, confirm the root cause is eliminated, and validate that the fix does not introduce regressions in related functionality.