diagnosing-bugs

Diagnose bugs and performance regressions using structured feedback loops and minimal repro scenarios.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/nseluga/os --skill diagnosing-bugs-nseluga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosing-bugs
Source: https://github.com/nseluga/os/tree/main/skills/diagnosing-bugs
Command: npx skills add https://github.com/nseluga/os --skill diagnosing-bugs-nseluga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnose hard-to-find bugs and performance regressions, helping developers identify and fix issues efficiently.

Core Features & Use Cases

  • Structured Diagnosis Loop: A step-by-step guide to building a tight feedback loop for diagnosing bugs.
  • Feedback Loop Construction: Offers various methods to construct a feedback loop, including failing tests, HTTP scripts, and headless browser scripts.
  • Minimal Repro Creation: Helps create minimal scenarios that still reproduce the bug, making it easier to isolate the problem.
  • Hypothesis Generation: Assists in generating falsifiable hypotheses to narrow down the cause of the bug.
  • Instrumentation and Logging: Provides guidance on how to instrument code and use targeted logging for debugging.
  • Regression Testing: Encourages writing regression tests before applying fixes to ensure the issue is resolved.

Quick Start

Run the 'diagnosing-bugs' skill to start diagnosing a bug in your codebase. Follow the structured steps provided in the Skill's guide.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I diagnose a hard-to-find bug or performance regression in my codebase?

To diagnose a hard bug, construct a tight feedback loop using failing tests or HTTP scripts, create a minimal reproduction scenario, generate falsifiable hypotheses, and apply structured debugging techniques to isolate the issue efficiently.

What is the best way to create a minimal reproduction scenario for a complex bug?

Creating a minimal reproduction scenario involves stripping away extraneous code and conditions until only the core triggers of the bug remain, which makes it significantly easier to isolate the exact cause of the performance regression or failure.

How do I build a tight feedback loop for debugging?

Build a tight debugging feedback loop by automating the reproduction of the issue using failing tests, HTTP scripts, or headless browser scripts, allowing you to rapidly verify hypotheses and observe the effects of code changes.

Do I need knowledge of specific debugging tools to use structured bug diagnosis?

Yes, structured bug diagnosis requires existing knowledge of debugging tools and methods, as well as the ability to write and execute scripts, to effectively instrument code, apply targeted logging, and validate falsifiable hypotheses.

Why should I write a regression test before applying a bug fix?

Writing a regression test before applying a fix ensures the failing test initially reproduces the bug and subsequently passes once the issue is resolved, verifying that the performance regression or error is completely eliminated.

How do I generate falsifiable hypotheses to narrow down the cause of a bug?

Generate falsifiable hypotheses by analyzing instrumentation and targeted logging data to propose specific, testable causes of the bug, then systematically validate or disprove each hypothesis using your minimal reproduction scenario.