diagnose

Guide systematic debugging with reproducibility, hypothesis generation, and regression testing.

1|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/bossjones/boss-skills --skill diagnose-bossjones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/bossjones/boss-skills/tree/main/.claude/skills/diagnose
Command: npx skills add https://github.com/bossjones/boss-skills --skill diagnose-bossjones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill unit addresses the complex process of diagnosing bugs and performance regressions by guiding through a structured and methodical approach, making it easier to find and fix issues in codebases.

Core Features & Use Cases

  • Disciplined Diagnostics: Offers a reproducible and methodical approach to diagnosis.
  • Reproducibility Loop: Constructs a feedback loop for quick identification of the bug or regression.
  • Phase-Based Strategy: Guides through specific phases including reproduction, hypothesis generation, and fix validation.
  • Use Case: Ideal for a developer facing a complex issue, where systematic analysis can help identify and fix the problem.

Quick Start

Execute the diagnose skill and follow the interactive guidance to reproduce, minimize, hypothesize, and instrument your bug, ultimately fixing and regression testing it.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically debug complex performance regressions in my codebase?

Systematic debugging of performance regressions requires a structured approach: reproduce the issue, generate hypotheses, instrument the code, and run regression testing. This methodical process identifies the root cause rather than guessing at symptoms.

What is a reproducibility loop and how does it help with bug tracking?

A reproducibility loop is a structured feedback cycle for bug tracking that consistently recreates the issue, tests a hypothesis, and validates the fix. It minimizes complex code analysis time by confirming reliable verification.

How do I generate and validate hypotheses during complex code analysis?

Hypothesis generation during code analysis involves forming targeted guesses about the bug's origin based on reproduced symptoms. You validate these hypotheses by instrumenting the code and observing outcomes through disciplined regression testing.

Can I use a phase-based strategy for diagnosing intermittent bugs?

Yes, a phase-based strategy is effective for intermittent bugs because it enforces disciplined diagnostics. Systematically moving through reproduction, minimization, and hypothesis validation reliably captures and fixes inconsistent issues.

What's the best way to approach code review for performance analysis and regressions?

The best approach to code review for performance analysis is integrating regression testing that validates fixes against the original issue. This phase-based strategy ensures the codebase remains stable and prevents future regressions.