reversa-debugger-debate

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-debugger-debate-gleisonoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-debugger-debate
Source: https://github.com/GleisonOliveira/dockerpilot-mcp/tree/main/.agents/skills/reversa-debugger-debate
Command: npx skills add https://github.com/GleisonOliveira/dockerpilot-mcp --skill reversa-debugger-debate-gleisonoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Single-pass debugging often produces fragile conclusions. This Skill orchestrates a structured multi-agent debate where N independent solvers argue over R rounds and an isolated judge with a frozen rubric synthesizes one recommendation for a registered bug's diagnosis, repair strategy, or spec verdict. ## 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, preventing echo chambers and reward hacking. - Auditable state and failure handling: all rounds, convergence metrics, and the final answer are written to the bug's debate folder, with hard timeouts, quorum rules, and explicit cost estimates before running. - Optional external harnesses: CLI agents like Codex or Gemini can join as solvers or critics, but only with explicit user consent and never for restricted-visibility bugs. - Use Case: A registered bug has three plausible root causes. Run the debate in diagnosis mode with 3 solvers and 2 rounds; the judge returns a synthesized hypothesis with a discriminating probe, which you then execute in the fix workflow. ## 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) for R rounds (default 2), then an isolated judge synthesizes the winning 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 and ends in a recommendation, with the final verdict left to a human.

Can external CLI agents like Codex or Gemini join the debate?▼

Yes, detected CLI harnesses can join as solvers or critics, but only after explicit user approval and a probe confirming non-interactive authenticated operation. Bugs marked visibility: restricted never allow external harnesses.

What happens when a debate participant times out or fails?▼

Each call has a hard 10-minute timeout with one retry for transport failures only. Failed participants produce a file with status timeout, error, or invalid-output, and the debate continues only if quorum of max(2, ceil(2N/3)) valid solvers is met.

Does the debate skill modify my project source code?▼

No. It writes only inside the bug's debate directory and never modifies pre-existing project files. It decides strategy; the actual fix is applied separately through the reversa-debugger-fix workflow.