diagnose

Guide software engineers through systematic debugging and hypothesis testing.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/hheydaroff/common-agent-skills --skill diagnose-hheydaroff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/hheydaroff/common-agent-skills/tree/main/skills/diagnose
Command: npx skills add https://github.com/hheydaroff/common-agent-skills --skill diagnose-hheydaroff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Identifies and streamlines the process of diagnosing hard bugs, crashes, and regressions by establishing effective feedback loops and systematic troubleshooting methods.

Core Features & Use Cases

  • Structured Debugging: Guides users through building deterministic test and reproduction loops.
  • Hypothesis Generation: Assists in generating falsifiable hypotheses to locate root causes.
  • Instrumentation & Fixing: Recommends targeted probing and regression test creation for reliable bug fixes.
  • Use Case: Developers troubleshooting intermittent failures can follow this skill to isolate the cause, verify fixes, and prevent regressions in complex systems.

Quick Start

Run structured debugging tests and create targeted instrument scripts to reproduce and fix challenging bugs.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically debug complex software bugs and crashes?

Structured debugging establishes effective feedback loops by guiding developers through building deterministic reproduction tests, generating falsifiable hypotheses for root cause isolation, and creating targeted regression tests to verify fixes and prevent future regressions.

What's the best way to troubleshoot intermittent performance regressions in my codebase?

Troubleshooting intermittent performance regressions requires systematic hypothesis testing and targeted instrumentation to isolate variables. By establishing structured feedback loops, you can verify fixes reliably and ensure reproducibility across complex systems without relying on guesswork.

How does hypothesis testing work when diagnosing software failures?

Hypothesis testing in software diagnosis works by generating falsifiable assumptions about the root cause of a failure. You systematically test each hypothesis through targeted probing and instrumentation, narrowing down the cause until the issue is isolated and fixed.

Do I need external debugging tools or dependencies to diagnose performance issues?

No external debugging tools or dependencies are required to diagnose performance issues using this approach. It focuses entirely on manual guidance, structured troubleshooting methods, and strategic instrumentation techniques applicable across any codebase or system environment.

When should I use systematic troubleshooting for bug tracking instead of standard debugging?

Systematic troubleshooting should be used for bug tracking when facing hard bugs, crashes, or regressions that resist standard debugging methods. It is specifically designed for intermittent failures and complex systems where establishing effective feedback loops is critical.