skills.rest
guhans6
guhans6COMMUNITY
Explore all skills by this author →
GitHub

diagnose

Guide structured bug diagnosis with reproduce, hypothesize, instrument, fix, and regression-test loops.

Updated May 11, 2026
Search Tags:#code analysis#debugging#bug diagnosis#systematic process#performance regression
One-click install
npx skills add https://github.com/guhans6/agent-workbench --skill diagnose-guhans6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/guhans6/agent-workbench/tree/main/shared/skills/diagnose
Command: npx skills add https://github.com/guhans6/agent-workbench --skill diagnose-guhans6

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a disciplined approach to diagnose hard bugs and performance regressions, guiding users through a systematic process to identify and resolve issues efficiently.

Core Features & Use Cases

  • Structured Process: Follows a disciplined loop of reproduce, hypothesise, instrument, fix, and regression-test.
  • Feedback Loops: Builds a fast, deterministic pass/fail signal for bugs.
  • Use Case: When encountering a bug or performance issue, this Skill helps to systematically identify the root cause and implement a fix.

Quick Start

Run the diagnose skill to start the bug diagnosis process.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically diagnose a hard bug or performance regression in my code?▼

To diagnose a bug or performance regression systematically, follow a structured process of reproducing the issue, hypothesizing causes, instrumenting code, applying fixes, and running regression tests.

What's the best way to build a fast feedback loop for bug diagnosis?▼

The best way to build a feedback loop for bug diagnosis is to establish a deterministic pass or fail signal by reproducing the issue consistently, allowing you to quickly validate hypotheses and code fixes.

How do I identify the root cause of a performance regression?▼

To identify the root cause of a performance regression, use a disciplined debugging loop: reproduce the regression, hypothesize potential causes, instrument the code to gather data, and verify the fix with regression testing.

What do I need to start a structured debugging process for a complex issue?▼

To start a structured debugging process, you need a clear bug reproducible scenario and access to the affected environment, enabling you to systematically instrument code and validate root cause hypotheses.

Why should I use a systematic process for code analysis instead of ad-hoc debugging?▼

A systematic process for code analysis ensures you build deterministic feedback loops and validate hypotheses methodically, resolving hard bugs and performance regressions more efficiently than ad-hoc debugging.

Does the diagnosis process work without a reproducible scenario?▼

The diagnosis process requires a clear bug reproducible scenario and access to the affected environment to build the deterministic feedback loops necessary for identifying and fixing the root cause.

Related Skills

Explore More Software Engineering Skills→
vladpolewoivladpolewoi

diagnose

Diagnose software bugs and performance regressions through structured hypothesis testing.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-investigate

Identify bug root causes through symptom collection, code path tracing, and deterministic reproduction.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
Himanshu040604Himanshu040604

sentry-dotnet-sdk

Integrate Sentry SDK for .NET error monitoring, tracing, and profiling.

Community
Intermediate