diagnose

Diagnose software bugs and performance regressions through a structured feedback loop.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/moonshineTP/ATTT-20252 --skill diagnose-moonshinetp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/moonshineTP/ATTT-20252/tree/main/.gemini/skills/diagnose
Command: npx skills add https://github.com/moonshineTP/ATTT-20252 --skill diagnose-moonshinetp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Disciplined Diagnosis Loop: A structured loop for reproducing, minimizing, hypothesizing, instrumenting, fixing, and regression-testing bugs.
  • Feedback Loop Construction: Methods to construct a fast, deterministic pass/fail signal for bugs.
  • Phase-Based Process: Steps to follow, including building a feedback loop, reproducing the bug, hypothesizing, instrumenting, fixing, and regression testing.
  • Use Case: When a user reports a bug or a performance issue, the Skill helps to diagnose the problem and implement a solution.

Quick Start

Run the diagnose skill and follow the steps to systematically diagnose a performance regression in your application.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I systematically diagnose a hard bug in my software application?▼

To systematically diagnose a hard bug, you must reproduce the issue, generate hypotheses, instrument the code, and test fixes within a local development or CI environment that supports code execution and logging.

What is the best way to isolate and fix a performance regression?▼

The best way to fix a performance regression is to follow a disciplined diagnosis loop that builds a fast, deterministic pass/fail signal, reproduces the bug, minimizes variables, and regression-tests the applied fix.

How do I construct a deterministic feedback loop for intermittent bug diagnosis?▼

Constructing a deterministic feedback loop for bug diagnosis involves instrumenting your code to reliably reproduce the issue and generate a consistent pass or fail signal for accurate regression testing.

Can I use this systematic debugging approach in a CI pipeline?▼

Yes, you can use this systematic debugging approach in a CI pipeline, as it requires an environment where code execution and logging can occur to effectively reproduce, instrument, and test fixes.

Why do I need to instrument code when diagnosing a performance regression?▼

You need to instrument code when diagnosing a performance regression to construct a fast, deterministic feedback loop that accurately captures pass/fail signals and validates your hypotheses during testing.

What are the limitations of disciplined bug diagnosis without code execution?▼

Without an environment that supports code execution and logging, disciplined bug diagnosis is limited because you cannot reproduce the issue, instrument the code, or test fixes to validate your hypotheses.