What problem does it solve?
Fixing bugs in legacy systems often loses the causal trail: no reproduction evidence, no regression tests, and no record of whether the code or the spec was wrong. This Skill takes a bug already registered by the Reversa debugger and drives it to a proven, traceable closure with human-approved gates.
Core Features & Use Cases
- Guided fix cycle: Reproduces the bug, establishes root cause with epistemic states (hypothesized, supported, confirmed), assesses change risk, and optionally triggers a multi-agent debate before fixing.
- Two-gate change control: Requires approval of reproduction/regression tests (demonstrated failing) and then the correction change set (demonstrated passing), with diffs saved per change item.
- Spec verdict and closure policy: Compares the fix against the effective spec, generates versioned spec addenda when needed, and closes the bug per the project's closure policy with a DONE.md lock.
- Use Case: After running /reversa-debugger to log a checkout bug, invoke this Skill with the bug ID to reproduce it, write failing tests, apply an approved minimal fix, and close it 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 and walk me through the gates.