diagnose

Automate software bug diagnosis with a structured feedback loop and regression testing.

1|Updated Aug 16, 2023
One-click install
npx skills add https://github.com/monlor/dotfiles --skill diagnose-monlor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/monlor/dotfiles/tree/main/config/ai/agents/skills/diagnose
Command: npx skills add https://github.com/monlor/dotfiles --skill diagnose-monlor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to diagnosing and resolving complex bugs and performance regressions, guiding the user through a disciplined diagnostic loop.

Core Features & Use Cases

  • Structured Debugging Process: Walks through a systematic approach to debugging, from building a feedback loop to cleaning up after fixing the bug.
  • Feedback Loop Construction: Offers guidance on creating efficient feedback loops for bug detection.
  • Use Case: Ideal for developers facing hard-to-reproduce bugs or performance issues that require an in-depth analysis of the codebase.

Quick Start

Execute the skill with "diagnose" to start the bug diagnosis process.

Frequently Asked Questions about diagnose

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

FAQPage Schema
What is a systematic approach to debugging hard-to-reproduce bugs?

A systematic debugging approach builds a reproducible feedback loop to consistently trigger the bug, hypothesizes root causes, instruments the codebase for deeper insights, applies a fix, and runs regression testing to verify the resolution.

How do I diagnose performance regressions in a complex codebase?

To diagnose performance regressions, construct an efficient feedback loop that reproduces the issue, analyze the codebase systematically, hypothesize the root causes, and instrument the system to gain deeper performance insights before applying fixes.

What's the best way to build a feedback loop for bug diagnosis?

The best way to build a feedback loop for bug diagnosis is to establish a consistent, reproducible process that reliably triggers the defect, enabling you to hypothesize root causes and verify fixes through systematic codebase analysis.

Can I use a structured debugging process for both code bugs and performance issues?

Yes, a structured debugging process effectively resolves both code bugs and performance issues by guiding you through reproducing the anomaly, hypothesizing root causes, instrumenting for insights, fixing the codebase, and cleaning up with regression testing.

When do I need a structured discipline for codebase analysis?

You need a structured discipline for codebase analysis when facing hard-to-reproduce bugs or performance regressions that require systematic root cause hypothesizing, code instrumentation, and rigorous regression testing rather than ad-hoc debugging.