diagnose

Diagnose and fix software bugs through reproduce, hypothesise, instrument, fix, and regression-test phases.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/Seth090502/osanwe-public --skill diagnose-seth090502
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/Seth090502/osanwe-public/tree/main/.claude/skills/diagnose
Command: npx skills add https://github.com/Seth090502/osanwe-public --skill diagnose-seth090502

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured, disciplined loop for diagnosing and fixing hard bugs and performance regressions in software development.

Core Features & Use Cases

  • Structured Diagnose Loop: A disciplined approach for hard bugs and performance regressions, including reproduce, hypothesise, instrument, fix, and regression-test phases.
  • Build Feedback Loop: Focuses on constructing a fast, deterministic agent-runnable pass/fail signal for bugs.
  • Adversarial Verification: Ensures high-quality analysis with a 4-lens verifier for each qualifying pattern.
  • Prediction Scoring & Calibration Loop: Backfills realized returns and computes rolling Brier scores for new logic vs shadow logic.
  • Semantic Retrieval Substrate: Uses a local HNSW vector index over agent-written layers for semantic retrieval.

Quick Start

Run the diagnose skill with the 'diagnose this' or 'debug this' command when a bug or performance regression is reported.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is the best way to diagnose and fix hard bugs in software development?

Structured bug diagnosis solves performance regressions by guiding you through reproduce, hypothesise, instrument, fix, and regression-test phases. It requires a disciplined approach and a fast, deterministic agent-runnable pass/fail signal to isolate and resolve the regression.

How do I build a deterministic pass/fail signal for bug diagnosis?

You build a deterministic pass/fail signal by constructing a fast, agent-runnable test that the structured debugging loop uses to verify hypotheses. This build feedback loop ensures the bug reproduction and subsequent fixes are validated automatically and reliably.

Can I use this structured debugging approach for performance regressions?

Yes, you can use this structured debugging approach for performance regressions. The diagnostic loop handles both hard bugs and performance regressions by applying the same disciplined reproduce, hypothesise, instrument, fix, and regression-test methodology to isolate the root cause.

How do you verify bug diagnosis quality during the debugging process?

You verify bug diagnosis quality during the debugging process using adversarial verification. The system applies a 4-lens verifier for each qualifying pattern to ensure high-quality analysis and prevent false positives before finalizing the fix.

What are the limitations of using a structured approach for software maintenance and bug fixing?

A limitation of this structured approach for software maintenance is that it requires a fast, deterministic pass/fail signal to function effectively. Without a reliable way to automatically reproduce the bug, the disciplined diagnostic loop cannot verify hypotheses or validate fixes.