reversa-debugger-debate

Runs multi-agent debates with isolated judge to decide bug diagnosis, repair, or spec verdicts.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-debugger-debate-ruggery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-debugger-debate
Source: https://github.com/Ruggery/OCR_Cartorio/tree/main/.agents/skills/reversa-debugger-debate
Command: npx skills add https://github.com/Ruggery/OCR_Cartorio --skill reversa-debugger-debate-ruggery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Debugging complex bugs often suffers from single-pass reasoning that misses root causes or picks risky fixes. This Skill orchestrates a structured multi-agent debate where N independent solvers argue over R rounds and an isolated judge synthesizes one auditable recommendation for a registered bug. ## Core Features & Use Cases - Three Debate Modes: diagnosis (competing causal hypotheses), repair (competing fix strategies), and spec (recommendation on whether code, tests, or spec is correct). - Isolated Judge with Frozen Rubric: the judge sees only anonymized, shuffled final proposals and applies a rubric frozen before the debate, preventing echo chambers and reward hacking. - Auditable State on Disk: every round, convergence metric, and the final synthesis is written under the bug's debate folder, with explicit quorum, timeout, and failure handling. - Optional External Harnesses: can include CLI agents like Codex or Gemini as debaters or critics, only with explicit user consent and never for restricted-visibility bugs. - Use Case: A registered bug has conflicting evidence about its root cause. Run the debate in diagnosis mode with 3 solvers and 2 rounds, then receive one judge-synthesized hypothesis with a discriminating probe to confirm it. ## Quick Start Ask the agent to run a multi-agent debate on bug BUG-20260715-A7K3 in diagnosis mode with the default 3 solvers and 2 rounds.

Frequently Asked Questions about reversa-debugger-debate

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

FAQPage Schema
How do I run a multi-agent debate to diagnose a bug?▼

Invoke the skill with a registered bug ID and choose diagnosis mode. It runs N independent solvers (default 3) over R rounds (default 2), then an isolated judge synthesizes one recommended hypothesis with a discriminating probe.

What is the difference between diagnosis, repair, and spec debate modes?▼

Diagnosis debates competing causal hypotheses against the evidence. Repair debates fix strategies once the cause is confirmed, weighing minimal change and regression risk. Spec debates whether code, tests, or spec is correct, ending in a recommendation only—the verdict decision stays human.

Can I include external CLI agents like Codex or Gemini in the debate?▼

Yes, but only with explicit consent after a probe confirms the CLI works non-interactively and is authenticated. External agents can occupy a solver seat or act as critics, and they are forbidden entirely for bugs with restricted visibility.

What happens when a debater fails or times out during a round?▼

Each call has a hard 10-minute timeout with one retry only for transport failures. A failed debater produces a file marked timeout, error, or invalid-output and is never silently replaced; if quorum drops below max(2, ceil(2N/3)), you choose to continue, retry, or cancel.

Does the debate stop early if the solvers converge?▼

No. Rounds are fixed epochs with no early stopping. Convergence is recorded per round in convergencia.md purely for audit, so the debate always completes the configured number of rounds before judging.

Does the debate skill modify project source code?▼

No. It writes only inside the bug's debate directory and produces a strategy recommendation. Applying the fix is a separate step handled by the debugger-fix flow after human approval.