diagnose

Guide users through a structured debugging loop to fix technical issues.

1|Updated May 14, 2026

Search Tags:#debugging #root cause analysis #bug fixing #diagnosis #systematic troubleshooting

Ready to run

npx skills add https://github.com/MarcoAntolini/cursor-sync --skill diagnose-marcoantolini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/MarcoAntolini/cursor-sync/tree/main/cursor-skills/diagnose
Command: npx skills add https://github.com/MarcoAntolini/cursor-sync --skill diagnose-marcoantolini

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps users navigate complex debugging scenarios by providing a structured diagnosis loop for any technical issue, ensuring a thorough and systematic approach to troubleshooting.

Core Features & Use Cases

Disciplined Diagnosis Loop: Guides through a step-by-step process to identify and resolve bugs or performance issues.
Feedback Loop: Builds a pass/fail signal to confirm or reject hypotheses.
Investigation: Carefully reads errors, checks recent changes, and gathers evidence.
Hypothesis Formation: Develops 3-5 falsifiable hypotheses ranked by likelihood.
Instrumentation & Fixing: Minimally instruments the system and fixes at the root cause.
Cleanup: Verifies the issue is resolved and removes instrumentation.
Use Case: When a user reports a bug, this Skill can be used to systematically diagnose the issue and propose a fix.

Quick Start

Run the 'diagnose' skill to begin the disciplined diagnosis loop for a reported bug.

Frequently Asked Questions about diagnose

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

FAQPage Schema

What is a structured approach for systematic debugging and root cause analysis?▼

Systematic debugging uses a disciplined diagnosis loop to investigate errors, build a reproducible feedback loop, form falsifiable hypotheses, and fix the root cause of technical issues.

How do I troubleshoot a complex bug when the root cause is unclear?▼

Troubleshoot an unclear root cause by reading errors carefully, checking recent changes, gathering evidence, and testing 3-5 ranked hypotheses to systematically isolate and resolve the bug.

How can I create a reproducible feedback loop to test debugging hypotheses?▼

Create a reproducible feedback loop by establishing a pass/fail signal that confirms or rejects your hypotheses, allowing you to systematically test assumptions and validate the root cause.

What is the best way to fix a technical issue at its source without introducing new problems?▼

Fix technical issues at the source by minimally instrumenting the system, applying the fix, verifying the issue is resolved, and cleaning up any added instrumentation to prevent side effects.

When should I use a disciplined diagnosis loop for bug fixing?▼

Use a disciplined diagnosis loop for bug fixing when a user reports a bug or performance issue that requires careful analysis, evidence gathering, and systematic troubleshooting to resolve.

Can I use this systematic troubleshooting approach for any technical issue?▼

Yes, this systematic troubleshooting approach guides you through a structured diagnosis loop for any technical issue, ensuring thorough investigation, hypothesis testing, and root cause resolution.