diagnose

Apply a six-phase debugging framework to resolve software defects and performance regressions.

3|Updated Jul 30, 2023
One-click install
npx skills add https://github.com/danielcopper/dotfiles --skill diagnose-danielcopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/danielcopper/dotfiles/tree/main/claude/.claude/skills/diagnose
Command: npx skills add https://github.com/danielcopper/dotfiles --skill diagnose-danielcopper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of aimless, unstructured debugging by providing a rigorous, step-by-step framework to isolate and resolve complex software bugs and performance regressions.

Core Features & Use Cases

  • Feedback Loop Construction: Prioritizes building deterministic, agent-runnable tests to verify bug reproduction.
  • Hypothesis-Driven Debugging: Enforces a structured approach of generating falsifiable hypotheses before applying instrumentation.
  • Regression Prevention: Ensures that fixes are validated with regression tests and that architectural improvements are identified to prevent recurrence.

Quick Start

Invoke the diagnose skill to begin a structured debugging session for the reported issue.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a systematic approach for root cause analysis and software debugging?

Systematic root cause analysis and software debugging require a structured, six-phase framework to isolate defects, prioritizing deterministic reproduction and falsifiable hypothesis generation before applying instrumentation.

How do I build a deterministic reproduction loop for a performance regression?

To build a deterministic reproduction loop for a performance regression, construct agent-runnable tests that define test seams and establish performance baselines, ensuring consistent and repeatable outcomes for verification.

How do I generate falsifiable hypotheses when troubleshooting a complex bug?

When troubleshooting a complex bug, generate falsifiable hypotheses by structuring your debugging loop to propose specific root causes before adding instrumentation, ensuring each assumption can be tested and verified.

Does structured debugging require a specific environment for reproducibility?

Yes, structured debugging requires a structured environment where you can define reproduction loops, test seams, and performance baselines to ensure deterministic outcomes and reliable defect verification.

What's the best way to prevent future software defects after fixing a bug?

The best way to prevent future software defects after fixing a bug is to validate fixes with regression tests and identify architectural improvements during a post-mortem analysis to ensure the issue does not recur.