diagnosing-bugs

Diagnose bugs and performance regressions using reproducible symptoms and falsifiable hypotheses.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Debugging often stalls on guesswork, unverified assumptions, and fixes that never get validated against the original symptom. This Skill structures bug and performance investigations so every hypothesis is testable, every fix is confirmed against the reported behavior, and intermittent failures are measured rather than chased blindly. ## Core Features & Use Cases - Hypothesis-driven investigation: Trace symptoms through actual callers, logs, domain contracts, and recent changes, testing the cheapest discriminating observation first. - Regression and performance checks: Build the smallest practical check (test, request, CLI invocation, UI flow, or replay) that exercises the reported behavior, with baselines for performance work. - Human-in-the-loop reproduction: Adapt the included scripts/hitl-loop.template.sh capture template when reproduction requires manual interaction, recording triggers and reproduction rates. - Use Case: A user reports that clicking Export intermittently throws an error. Use this Skill to trace the callers, form falsifiable hypotheses, run the HITL capture script to record the error, fix the shared root cause, and re-run the original scenario with a focused regression check. ## Quick Start Use the diagnosing-bugs skill to investigate why the export button intermittently throws an error and confirm the fix with a regression check.

Frequently Asked Questions about diagnosing-bugs

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

FAQPage Schema
How do I diagnose an intermittent bug that is hard to reproduce?

Record the trigger conditions and reproduction rate before and after any change. If reproduction needs manual interaction, adapt the included hitl-loop.template.sh script to capture user observations as structured KEY=VALUE output.

How to investigate a performance regression before optimizing?

Establish a baseline under comparable conditions first, then form falsifiable hypotheses about the cause. Test the cheapest discriminating observation before changing code, and re-measure against the baseline after the fix.

What makes a good regression check for a bug fix?

A regression check must exercise the originally reported behavior, not merely the new helper or the absence of an exception. Use the smallest practical check: a test, request, CLI invocation, UI flow, or replay.

Can I debug without full access or a complete reproducer?

Yes, read-only investigation can continue while access or a full reproducer is missing. Trace callers, logs, and recent changes, but clearly distinguish a suspected cause from a confirmed one in your report.

When should I use the human-in-the-loop capture script?

Use it when reproduction requires manual interaction, such as clicking through a UI flow. Copy scripts/hitl-loop.template.sh, edit the step and capture prompts, and run it in a non-production environment unless separately authorized.