Diagnose complex software bugs through a structured 6-phase debugging workflow.
npx skills add https://github.com/docs-plus/docs.plus --skill diagnose-docs-plus
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/diagnose Command: npx skills add https://github.com/docs-plus/docs.plus --skill diagnose-docs-plus
This skill eliminates unproductive, ad-hoc debugging for complex, hard-to-reproduce bugs and performance regressions that waste engineering time and often lead to incomplete, recurring fixes.
Use the diagnose skill to debug the intermittent 500 error that occurs when uploading large files to the production API.
High-intent search queries and answers about installing and using this skill.
Debug hard-to-reproduce software bugs efficiently by following a structured 6-phase disciplined workflow that builds deterministic reproduction loops, generates falsifiable hypotheses, and adds regression tests to ensure durable fixes.
The best way to create a reproduction loop for flaky test failures is using prioritized methods like failing tests, headless browser scripts, and bisection harnesses to build fast, deterministic, agent-runnable loops.
Falsifiable hypothesis testing for root cause analysis works by generating targeted assumptions about defect sources, instrumenting specific code paths, and validating or rejecting hypotheses within a structured debug loop.
Yes, you can use this disciplined workflow for post-deployment production incidents, as it applies to software engineering workflows including opaque defect reports, intermittent errors, and performance regressions under specific load conditions.
Incomplete bug fixes keep recurring because ad-hoc debugging often misses the root cause, whereas a disciplined workflow enforces hypothesis generation, targeted instrumentation, and regression test implementation to prevent recurrence.
No, this debugging approach does not strictly require existing test infrastructure, as it provides guidance to build load test reproduction loops and bisection harnesses from scratch for investigating performance regressions under high concurrent load.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
davekilleenGenerate structured incident post-mortems with root cause analysis and action items.
JohannesKoningsDiagnose software bugs and performance regressions through deterministic feedback loops.
NagyViktConfigure structured logging, tracing, and performance monitoring for Vercel-hosted applications.
