diagnose

Diagnose hard bugs and performance regressions through a structured debugging loop.

2|Updated May 9, 2026
One-click install
npx skills add https://github.com/JohnRobert-Olano/3DwebsiteContemporyWorld --skill diagnose-johnrobert-olano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/JohnRobert-Olano/3DwebsiteContemporyWorld/tree/main/.agents/skills/diagnose
Command: npx skills add https://github.com/JohnRobert-Olano/3DwebsiteContemporyWorld --skill diagnose-johnrobert-olano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnose hard bugs and performance regressions, guiding users through a systematic process to efficiently find and fix issues.

Core Features & Use Cases

  • Disciplined Diagnosis Loop: A step-by-step process for reproducing, hypothesizing, and fixing bugs.
  • Build a Feedback Loop: Focuses on creating a reliable reproducible test to accelerate debugging.
  • Reproduce the Bug: Ensures the loop accurately reflects the user's description of the issue.
  • Hypothesize Causes: Encourages forming falsifiable hypotheses based on observations.
  • Instrumentation: Uses targeted debugging tools and logging for precise information.
  • Fix and Regression Test: Implements fixes and verifies them with regression tests.
  • Cleanup and Post-Mortem: Ensures a clean and informative bug fix for future reference.

Quick Start

To diagnose a performance issue, use the diagnose skill and follow the steps: build a feedback loop, reproduce the issue, hypothesize causes, instrument the code, fix the issue, and regression test the solution.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a structured approach to debugging hard bugs and performance regressions?

A structured debugging approach systematically reproduces, minimizes, hypothesizes, instruments, fixes, and regression-tests hard bugs. It builds a reliable feedback loop to efficiently find and resolve complex system failures or slow performance issues.

How do I debug a performance regression using a disciplined diagnosis loop?

To debug a performance regression, follow a disciplined diagnosis loop: build a feedback loop, reproduce the issue, form falsifiable hypotheses, instrument the code, apply a fix, and verify the solution with regression tests.

How do I create a reliable reproduction test for an unresponsive application?

Creating a reliable reproduction test for an unresponsive application requires building a feedback loop that accurately reflects the issue description. This ensures the debugging loop consistently triggers the system failure for precise instrumentation.

What do I need to diagnose slow performance and system failures in my codebase?

Diagnosing slow performance and system failures requires access to the codebase, execution environment, and debugging tools. This setup enables targeted instrumentation to gather precise information for forming falsifiable hypotheses.

When should I use hypothesis-driven bug diagnosis instead of ad-hoc debugging?

Use hypothesis-driven bug diagnosis when facing hard bugs or performance regressions that resist ad-hoc debugging. It encourages forming falsifiable hypotheses based on observations, ensuring targeted instrumentation and clean regression testing.

What should I do after fixing a bug to prevent future performance regressions?

After fixing a bug, implement regression tests to verify the solution and conduct a post-mortem. This cleanup ensures a clean, informative bug fix record that prevents future performance regressions and aids future debugging.