reversa-debugger-fix

Fixes registered bugs through reproduction, root-cause analysis, gated test and change-set approval.

1.5k|405|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-debugger-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-debugger-fix
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-debugger-fix
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-debugger-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about reversa-debugger-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a bug registered with reversa-debugger?

Run /reversa-debugger-fix with the bug ID or display number, such as /reversa-debugger-fix BUG-20260715-A7K3. Without an argument, the Skill computes impact scores across open bugs and suggests the highest-impact one for you to choose.

What is the bug fixing workflow in this Skill?

The cycle covers optional mitigation, reproduction with an evidence capsule, root-cause diagnosis with epistemic states, change-risk assessment, a mandatory visual fix plan, two approval gates for tests and the change set, a spec verdict, and closure per the project policy.

Can I use this Skill without registering a bug first?

No. The Skill aborts if the _reversa_bugs/ registry does not exist and instructs you to run /reversa-debugger first. Every fix must trace back to a registered bug record.

Does the Skill modify project files automatically?

No. Every change to the project passes through approval gates with diffs shown first. Outside the gates it only writes to _reversa_bugs/ and spec addenda folders, and original specs remain read-only.

What happens if a bug cannot be reproduced?

The Skill never invents a cause. It offers to close the bug as instrumentation-required, where the change set adds logging, metrics, or tracing to capture the next occurrence, treating instrumentation as a valid fix.

Which AI coding agents support this Skill?

The Skill declares compatibility with Claude Code, Codex, Cursor, Gemini CLI, and other agents compatible with the Agent Skills format. It is installed by the Reversa framework into .agents/skills/ or .claude/skills/.