diagnose-bugs

Diagnose complex bugs and performance issues with systematic hypothesis testing.

1|1|Updated Mar 10, 2013
One-click install
npx skills add https://github.com/aaronlord/.dotfiles --skill diagnose-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-bugs
Source: https://github.com/aaronlord/.dotfiles/tree/main/pi/skills/diagnose-bugs
Command: npx skills add https://github.com/aaronlord/.dotfiles --skill diagnose-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill assists in identifying and diagnosing difficult bugs and performance issues efficiently.

Core Features & Use Cases

  • Sentry Issue Handling: Provides guidance on dealing with Sentry issues from detection to resolution.
  • Feedback Loop Construction: Offers techniques to create a robust feedback loop for identifying and verifying bugs.
  • Reproduction and Minimization: Aids in reproducing and minimizing the problem to a smallest reproducible case.
  • Hypothesis Testing: Generates falsifiable hypotheses to guide the debugging process.
  • Instrumentation: Utilizes various tools for in-depth investigation and verification of bugs.
  • Regression Testing: Ensures the bug is fixed and can be detected again through regression tests.

Quick Start

To start diagnosing a bug, run the diagnose-bugs skill with the command "diagnose-bugs" followed by the relevant context.

Frequently Asked Questions about diagnose-bugs

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

FAQPage Schema
How do I diagnose hard bugs and performance regressions using systematic debugging methods?

To diagnose hard bugs and performance regressions, you generate falsifiable hypotheses and construct robust feedback loops to systematically narrow down root causes. This structured approach guides targeted investigation and verification.

What is the best way to handle Sentry issues from detection to resolution?

The best way to handle Sentry issues is to follow a systematic workflow from detection through reproduction, minimization, and hypothesis testing to final resolution. This ensures thorough investigation and verification before fixing.

How do I reproduce and minimize a complex bug to a smallest reproducible case?

To reproduce and minimize a complex bug, you systematically strip away irrelevant variables while maintaining the error condition. This process isolates the exact trigger, creating a minimal reproducible case for easier hypothesis testing.

Why do I need falsifiable hypotheses when troubleshooting post-deployment performance issues?

You need falsifiable hypotheses when troubleshooting post-deployment performance issues because they provide a structured, testable framework for investigation. This prevents random guessing and focuses debugging efforts on verifying specific root cause theories.

How do I ensure a fixed bug is detected again through regression testing?

To ensure a fixed bug is detected again, you implement regression tests that validate the original error condition is resolved. This creates a safety net that automatically catches the bug if it reappears in future deployments.