What problem does it solve? Fixing bugs without a disciplined process leads to untracked changes, unproven root causes, and regressions that resurface later. This Skill takes a bug already registered in the Reversa framework and drives it from triage to verified closure with causal evidence, approved change sets, and spec alignment. ## Core Features & Use Cases - Guided bug-fix lifecycle: reproduction capsule, root-cause analysis with epistemic states (hypothesized/supported/confirmed), optional git bisect for regressions, and risk assessment before any change. - Two-gate approval workflow: reproduction and regression tests are approved and shown failing first, then the typed correction change set (code, configuration, migration, data-repair, specification) is approved and shown passing. - Spec verdict and closure policy: compares the fix against the effective spec, generates versioned addenda when needed, and closes the bug per the project's closure policy (local-software, package, or production-service) with a DONE lock. - Use Case: A developer runs /reversa-debugger-fix BUG-007 to reproduce a reported defect, prove the root cause with evidence, apply a minimal approved patch with regression tests, 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 debugging workflow.
