diagnose

Guide a phase-based debugging loop from reproduction to validated fix.

Updated Jul 2, 2026

Search Tags:#debugging #instrumentation #diagnose #phases #root-cause #bug-reproduction

Ready to run

npx skills add https://github.com/SamyakJhaveri/loam --skill diagnose-samyakjhaveri

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/SamyakJhaveri/loam/tree/main/cultivation/marketplace/pocock-engineering/skills/diagnose
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill diagnose-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disciplined, phase-based debugging loops that convert vague bug reports into actionable fixes by reproducing, hypothesising, instrumenting, and validating regression tests.

Core Features & Use Cases

Phase-based workflow: Build a fast feedback loop, reproduce, hypothesise, instrument, fix, and validate.
Deterministic repro and guardrails: Structured steps reduce flakiness and accelerate root-cause analysis.
Use Case: When a user reports a hard bug or performance regression, the skill guides the team from reproduction to a validated fix.

Quick Start

Follow Phase 1 to establish a reproducible repro and begin the six-phase diagnosis loop.

Frequently Asked Questions about diagnose

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

FAQPage Schema

How do I debug a hard bug that is difficult to reproduce?▼

Debugging a hard bug requires a disciplined, phase-based diagnosis loop that moves from establishing a reproducible reproduction to hypothesising, instrumenting, fixing, and validating regression tests.

What is the best way to perform root-cause analysis on flaky integration failures?▼

Root-cause analysis on flaky failures uses a structured, phase-based workflow with deterministic repro guardrails and hypothesis-driven testing to reduce flakiness and isolate the actual defect.

Can I use a structured debugging loop for performance regressions?▼

A structured debugging loop applies to performance regressions by guiding teams through explicit phase steps, instrumentation, and regression verification to convert vague reports into validated fixes.

Does hypothesis-driven testing work for end-to-end bug investigations?▼

Hypothesis-driven testing works for end-to-end bug investigations by enforcing a reproducible loop that builds fast feedback, instruments the system, and validates fixes against regressions.

What are the limitations of a phase-based debugging loop?▼

Phase-based debugging loops require a deterministic reproduction to function effectively; without establishing a reproducible state in the initial phase, the subsequent hypothesising and instrumentation steps cannot reliably isolate the root cause.

Do I need specific instrumentation tools to start a guided debugging loop?▼

You do not need specific external instrumentation tools to start; the guided debugging loop defines the instrumentation phase as a structural step where you add the necessary diagnostic logic to validate your hypotheses.