diagnose

Diagnose and fix software bugs and performance regressions using structured debugging techniques.

9|Updated May 25, 2026
One-click install
npx skills add https://github.com/wzser/supermatrix --skill diagnose-wzser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/wzser/supermatrix/tree/main/platform/skill-master/skills/diagnose
Command: npx skills add https://github.com/wzser/supermatrix --skill diagnose-wzser

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill aids in efficiently diagnosing and resolving hard bugs and performance regressions, providing a structured approach to problem-solving in software development.

Core Features & Use Cases

  • Structured Debugging Loop: Follows a disciplined loop of reproduce, minimize, hypothesize, instrument, fix, and regression-test.
  • Feedback Loop Construction: Assists in building a fast, deterministic, agent-runnable pass/fail signal for the bug.
  • Non-Deterministic Bug Handling: Strategies for increasing the reproduction rate of non-deterministic bugs.
  • Instrumentation and Fixing: Offers guidance on using debuggers, targeted logs, and performance measurement for fixing and verifying the issue.

Quick Start

Use the /new command to create a session, then run the /status command to check the session status.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically diagnose and fix hard bugs in software development?

Systematically diagnose and fix hard bugs by following a structured debugging loop: reproduce, minimize, hypothesize, instrument, fix, and regression-test. This approach builds a fast, deterministic pass/fail signal to verify the issue is resolved.

What is the best way to increase the reproduction rate of non-deterministic bugs?

To increase the reproduction rate of non-deterministic bugs, apply specialized strategies to build a deterministic feedback loop. This involves targeted instrumentation and adjusting the environment to reliably trigger the issue for diagnosis.

How does a structured debugging loop help resolve performance regressions?

A structured debugging loop resolves performance regressions by enforcing a disciplined process of measuring performance, hypothesizing the cause, instrumenting the code, and verifying the fix. This ensures regressions are systematically isolated and resolved.

Do I need access to specific debugging tools and project ADRs to diagnose issues?

Yes, diagnosing issues requires access to debugging tools and the project environment, as well as knowledge of the project's domain and Architecture Decision Records (ADRs) to accurately reproduce and hypothesize the root cause.

Why should I use a structured approach instead of ad-hoc logging for bug diagnosis?

A structured approach ensures a disciplined loop of reproduction and regression testing, whereas ad-hoc logging lacks a deterministic pass/fail signal. It guides you to build a fast feedback loop, instrument correctly, and verify fixes reliably.

What are the limitations of diagnosing bugs without a minimized reproduction case?

Without a minimized reproduction case, bug diagnosis becomes inefficient and lacks a deterministic pass/fail signal. The structured debugging loop requires minimizing the issue to build a fast, agent-runnable feedback signal for accurate fixing.