diagnosing-bugs

Construct feedback loops to diagnose hard-to-reproduce bugs and performance regressions.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill diagnosing-bugs-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions/tree/main/upstream-snapshots/mattpocock-skills/skills/engineering/diagnosing-bugs
Command: npx skills add https://github.com/tgmarinho/agent-super-powers-matt-pocock-skills-comparasions --skill diagnosing-bugs-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill offers a systematic approach to diagnose hard bugs and performance regressions, reducing time to resolution and enhancing debugging efficiency.

Core Features & Use Cases

  • Feedback Loop Construction: Build and refine a feedback loop to quickly identify and reproduce the issue.
  • Reproduction and Minimization: Reproduce the bug and minimize the scenario to isolate the problem.
  • Hypothesis and Instrumentation: Generate and test hypotheses, using targeted logs and debugging tools.
  • Regression Test and Cleanup: Write and run a regression test before and after the fix, ensuring the issue is resolved.
  • Use Case: Ideal for software engineers facing difficult-to-reproduce bugs in complex systems, where a structured and methodical approach is needed.

Quick Start

Execute the script to initiate the diagnosis loop for a specific bug: ./scripts/diagnose-bug.sh

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
What is the best way to diagnose hard-to-reproduce bugs in complex systems?

Bug diagnosis in complex systems is systematized by constructing and refining a feedback loop to quickly identify, reproduce, and isolate the issue. This structured approach reduces time to resolution by methodically minimizing the problem scenario before applying fixes.

How do I create a feedback loop for software debugging and performance regression?

To create a debugging feedback loop, you reproduce the bug and minimize the scenario to isolate the root cause. You then generate hypotheses and use targeted logs and debugging tools to test them, ensuring accurate performance regression identification and resolution.

Can I use this structured approach for performance regressions as well as logic bugs?

Yes, this structured approach targets both hard-to-reproduce bugs and performance regressions. It provides systematic methods for hypothesis testing and scenario minimization, making it ideal for diagnosing complex software engineering issues across different system failure types.

How do I write a regression test after isolating a bug?

After isolating a bug, you write and run a regression test before and after applying the fix. This ensures the issue is actually resolved and prevents future performance regressions or the recurrence of hard-to-reproduce bugs in the system.

What are the limitations of using a feedback loop for bug diagnosis?

The feedback loop approach requires methodical hypothesis testing and scenario minimization, which can be time-consuming. It is designed for difficult-to-reproduce bugs and performance regressions, meaning simpler issues might not need such a structured debugging process.