What problem does it solve? It takes a bug already registered in the Reversa bug registry and drives it to a verified, auditable closure: reproduction with evidence, root-cause tracking, approved change sets, regression tests, and a spec verdict, instead of ad-hoc untracked fixes. ## Core Features & Use Cases - Guided fix lifecycle: reproduction capsule, epistemological root-cause states (hypothesized/supported/confirmed), optional git bisect regression analysis, and impact-based bug selection across contexts. - Two approval gates: test diffs must be approved and shown failing before the correction change set is approved and shown passing, with all diffs saved under fix/. - Spec verdict and closure policy: compares the fix against the effective spec, generates versioned addenda when needed, and locks the bug folder with a DONE.md marker once the closure policy is satisfied. - Use Case: After registering a checkout bug with /reversa-debugger, run this skill to reproduce it, write failing regression tests, apply a minimal approved patch, and close the bug with full traceability. ## Quick Start Ask the agent to fix a registered bug by running /reversa-debugger-fix with the bug ID, for example: fix BUG-20260715-A7K3 following the Reversa workflow.
