skills.rest
henrycashe26
henrycashe26COMMUNITY
Explore all skills by this author →
GitHub

diagnose

Structure debugging with hypothesis generation and regression testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of aimless, trial-and-error debugging by providing a structured, scientific framework to isolate and resolve complex software bugs and performance regressions.

Core Features & Use Cases

  • Feedback Loop Construction: Guides you through creating deterministic reproduction signals, from unit tests to headless browser scripts.
  • Hypothesis-Driven Debugging: Enforces a rigorous process of generating falsifiable hypotheses before making code changes.
  • Use Case: When a user reports a non-deterministic performance regression, use this skill to build a high-frequency reproduction loop, isolate the bottleneck, and verify the fix with a regression test.

Quick Start

Use 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 isolate non-deterministic performance regressions without guessing?▼

Isolate performance regressions by building a deterministic feedback loop using high-frequency reproduction scripts. This framework enforces generating falsifiable hypotheses and instrumentation before modifying code to pinpoint exact bottlenecks.

What is hypothesis-driven debugging and how does it resolve complex software bugs?▼

Hypothesis-driven debugging is a structured approach requiring you to generate falsifiable hypotheses before making code changes. It ensures systematic reproduction and verification, replacing aimless trial-and-error with permanent bug resolution.

How do I create a deterministic feedback loop for an intermittent timeout error?▼

Create a deterministic feedback loop by constructing reproduction signals ranging from unit tests to headless browser scripts. This captures the intermittent timeout consistently, allowing you to verify the fix with a regression test.

What's the best way to troubleshoot root cause analysis for an unreliable checkout service?▼

The best way to perform root cause analysis is applying a disciplined, repeatable loop for crushing bugs. It guides systematic reproduction, instrumentation, and verification to ensure permanent resolution of complex issues across environments.

Do I need specific testing frameworks to reproduce bugs across various technical environments?▼

No specific testing frameworks are required. You can construct deterministic reproduction signals from unit tests to headless browser scripts, adapting the feedback loop to your existing technical environment and instrumentation tools.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
JamieMasonJamieMason
2.1k

fix-bug

Reproduces and debugs issues in the Swagger codebase using AI-powered analysis and automated correction suggestions.

Community
Advanced
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic