skills.rest
cloudofgeorge
cloudofgeorgeCOMMUNITY
Explore all skills by this author →
Website𝕏@cloudofgeorgeGitHub

diagnose

Reproduce, instrument, and fix bugs with regression testing.

Updated May 11, 2026
Search Tags:#testing#debugging#regression#instrumentation#diagnose#reproduction#bug
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill diagnose-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/diagnose
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill diagnose-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill provides a disciplined, repeatable loop to diagnose hard bugs and performance regressions by reproducing the issue, minimising its surface, hypothesising causes, instrumenting the code, implementing fixes, and validating with regression tests.

Core Features & Use Cases

  • Structured diagnostic loop: reproduce, minimise, hypothesise, instrument, fix, and regression-test.
  • Guidance for building deterministic, reproducible loops using scripts in scripts/ and ADRs to guide root cause analysis.
  • Use Case: when a user reports a bug or slowdown, run the loop to isolate the failure and verify a fix across environments.

Quick Start

Describe the bug and run the deterministic diagnostic loop using the included script to reproduce, instrument, hypothesise, fix, and regression-test.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a disciplined diagnostic loop for bug reproduction?▼

A disciplined diagnostic loop is a repeatable process to reproduce bugs, minimize their surface, hypothesize causes, instrument code, implement fixes, and validate with regression tests.

How do I diagnose hard bugs and performance regressions across environments?▼

You diagnose hard bugs and performance regressions by running a deterministic diagnostic loop using included scripts to reproduce the issue, instrument code, hypothesize causes, fix, and verify regression coverage across environments.

Can I use scripts to guide root cause analysis for code regressions?▼

Yes, you can use included scripts and architecture decision records to guide root cause analysis, building a deterministic, reproducible loop for code regressions.

What's the best way to isolate a reported bug or slowdown for fast diagnosis?▼

The best way to isolate a reported bug or slowdown is to apply a structured diagnostic loop: reproduce the issue, minimize its surface, hypothesize causes, instrument the code, implement fixes, and validate with regression tests.

When should I not use a repeatable diagnostic loop for debugging?▼

A repeatable diagnostic loop for debugging is not suited for non-reproducible issues or one-off errors where deterministic reproduction and regression test validation are impossible.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
Design-System-ETDesign-System-ET

debugging-wizard

Parse error messages and stack traces to isolate root causes.

Official
Advanced
icartshicartsh
4

error-detective

Parse stack traces and guide error resolution with the TRACE framework.

Community
Advanced