diagnose

Diagnose and fix software bugs and performance regressions through a structured six-phase loop.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill equips you with a structured approach to diagnose and fix complex bugs and performance regressions efficiently.

Core Features & Use Cases

  • Disciplined Diagnosis Loop: A systematic process for identifying and resolving hard bugs and performance issues.
  • Reproduce, Minimise, Hypothesise, Instrument, Fix, Regression-Test: A six-phase approach to tackle debugging challenges.
  • Feedback Loop Construction: Focus on building a fast, deterministic, and reproducible feedback loop to quickly identify the root cause.
  • Instrumentation and Analysis: Utilize targeted logs and debugging tools to understand the behavior of the system.
  • Regression Testing: Ensure that the fix does not introduce new issues and maintains system integrity.

Quick Start

Run the 'diagnose' skill with a failing test or a performance issue. Follow the structured diagnosis loop to identify and fix the problem.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I approach structured debugging for complex software bugs?

Structured debugging uses a disciplined diagnosis loop to identify and resolve hard bugs, requiring you to reproduce, minimize, hypothesize, instrument, fix, and regression-test the issue systematically.

What is the best way to diagnose performance regressions in software systems?

Diagnosing performance regressions requires constructing a fast, deterministic feedback loop, utilizing targeted instrumentation and debugging tools to analyze system behavior, and performing regression testing to verify the fix.

How do I build a feedback loop to find a root cause during bug diagnosis?

Building a feedback loop for bug diagnosis involves reproducing and minimizing the issue to create a deterministic cycle, allowing you to rapidly test hypotheses and instrument the system to pinpoint the root cause.

Can I use this systematic debugging approach for any software system?

This systematic debugging approach suits developers facing complex issues in software systems, but it requires the ability to construct feedback loops, utilize debugging tools, and perform regression testing independently.

Why do I need regression testing after fixing a hard bug?

Regression testing is needed after fixing a hard bug to ensure the fix does not introduce new issues and maintains overall system integrity throughout the software system.

What should I do when standard debugging is not working for hard bugs?

When standard debugging fails on hard bugs, switch to a disciplined six-phase approach: reproduce, minimize, hypothesize, instrument, fix, and regression-test, focusing on building a fast, deterministic feedback loop.