Diagnose bugs and performance regressions through a structured reproduce-hypothesise-fix workflow.
npx skills add https://github.com/Oatse/CWE-Automation --skill diagnose-oatse
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/diagnose Command: npx skills add https://github.com/Oatse/CWE-Automation --skill diagnose-oatse
[DEBUG-xxxx] prefix so cleanup is a single grep, plus a post-mortem checklist covering regression tests and architectural findings. - Use Case: A user reports "the export button throws intermittently." The Skill builds a loop that raises the reproduction rate, bisects the cause, writes a regression test at the correct seam, and verifies the fix against the original scenario. ## Quick Start Ask the agent to diagnose the bug where the export button intermittently throws an error and have it build a reproduction loop first.High-intent search queries and answers about installing and using this skill.
Raise the reproduction rate instead of chasing a clean repro: loop the trigger 100 times, parallelise, add stress, narrow timing windows, or inject sleeps. A 50%-flake bug is debuggable; keep increasing the rate until your feedback loop fires reliably.
Build a fast, deterministic pass/fail signal first: a failing test, a curl script against a dev server, a CLI invocation with fixture input, or a headless browser script. Confirm the loop reproduces the exact symptom the user described before hypothesising causes.
Stop and say so explicitly rather than guessing. Ask the user for environment access, a captured artifact such as a HAR file, log dump, or core dump, or permission to add temporary production instrumentation.
Establish a baseline measurement first using a timing harness, performance.now(), a profiler, or a query plan, then bisect to find the regression point. Logs are usually the wrong tool for performance work; measure first, fix second.
Write the regression test before the fix, but only at a correct seam that exercises the real bug pattern as it occurs at the call site. If no correct seam exists, document that as an architectural finding rather than writing a shallow test.
abrahamgreysonTrace code paths and validate hypotheses to identify root causes of software bugs.
janpeterdLocate shallow modules and propose deepened interfaces for codebase architecture.
shogo-labsMonitor live web app health via console errors, performance, and page failures.
Euda1mon1aDetect and correct code defects across test suites, linters, type checkers, and security scanners.