skills.rest
druejaramillo
druejaramilloCOMMUNITY
Explore all skills by this author →
GitHub

diagnose

Diagnose software bugs and performance regressions through hypothesis testing and regression verification.

Updated May 3, 2026
Search Tags:#automation#testing#performance#debugging#troubleshooting#root cause analysis
One-click install
npx skills add https://github.com/druejaramillo/skills --skill diagnose-druejaramillo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/druejaramillo/skills/tree/main/project/diagnose
Command: npx skills add https://github.com/druejaramillo/skills --skill diagnose-druejaramillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a rigorous, disciplined framework for identifying and resolving complex bugs and performance regressions that resist simple fixes.

Core Features & Use Cases

  • Feedback Loop Construction: Guides you in creating deterministic, automated tests to isolate failure signals.
  • Hypothesis-Driven Debugging: Enforces a structured approach to generating, ranking, and testing falsifiable hypotheses.
  • Use Case: Use this when you encounter a critical production bug or a performance regression and need a systematic, repeatable process to move from symptom to root cause and verified fix.

Quick Start

Invoke the diagnose skill to help me reproduce and fix the intermittent timeout error occurring in the checkout service.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug a complex production bug that resists simple fixes?▼

Isolate performance regressions by building deterministic automated tests that capture failure signals, ranking potential hypotheses, and verifying fixes through safe instrumentation and regression testing.

What is hypothesis-driven debugging and how does it work?▼

Hypothesis-driven debugging is a structured approach that enforces generating, ranking, and testing falsifiable hypotheses to systematically move from an observed software symptom to a verified root cause.

Can I use this diagnostic methodology for intermittent timeout errors?▼

Yes, you can use this diagnostic methodology for intermittent timeout errors by creating deterministic, automated tests to isolate the failure signals and establish a repeatable process to reproduce the issue.

Does this troubleshooting process require specific testing frameworks?▼

No specific testing frameworks are required as dependencies; the process focuses on applying disciplined root-cause analysis, safe instrumentation practices, and regression verification within your existing technical environment.

When should I use a structured root cause analysis over standard debugging?▼

Use structured root cause analysis when encountering critical software bugs or performance regressions that resist simple fixes and require a systematic, repeatable process to move from symptom to verified fix.

Related Skills

Explore More Software Engineering Skills→
AmidVoshakulAmidVoshakul

debugger

Analyze stack traces to isolate failure points and propose code fixes.

Community
Intermediate
gonz0wgonz0w
1

debugger-verification

Validate bug fixes using a formal five-criteria verification framework.

Community
Advanced
hachejhachej
45

diagnosing-bugs

Guide six-phase debugging to reproduce, isolate, and verify software bug fixes.

Community
Advanced
GuitarAlchemistGuitarAlchemist

reproduce-bug

Automate bug reproduction from GitHub issues with Playwright and log inspection.

Official
Intermediate