repro

# repro — symptom in, structured bug report out A raw symptom ("the decisions page is blank") is a weak fix prompt: it forces whoever fixes it to re-derive the environment, the steps, and the expected behavior from scratch, and it leaves nothing behind to prove the bug stays fixed. A **structured bug report** front-loads that work once, turns into a sharp fix prompt, and — its highest-value output — becomes a **failing regression test** that pins the defect forever. This skill produces that report, then offers to scaffold the test. It does **not fix the bug** — capturing it cleanly is the whole job; hand the report to the fix (or to `/systematic-debugging`) afterward. ## The report format — use this exact structure Emit the report as one **contiguous, pasteable block** (no leading `>` quote markers, no mid-sentence line breaks — Wes pastes these into prompts and issues): ``` ## BUG: <one-line summary — the observable failure, not the guessed cause> **Severity:** <blocker | major | minor — blocker = data loss/security/prod down> **Surface:** <page + click path, or route, or CLI command, or SDK method> **Environment** - Commit: <short sha> (<branch>) - Node: <version> · Platform: <os> - Package/SDK version: <if relevant> - Browser: <only if a UI bug> **Steps to reproduce** 1. <exact, replayable step — real values, not "do the thing"> 2. ... 3. ... **Actual** <what happens — verbatim error, status code, stack line, screenshot ref> **Expected** <what should happen, an...