debug-duel

Coordinate adversarial debugging rounds and audit opponent bug lists.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/ponsde/multi-agent-workflow --skill debug-duel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-duel
Source: https://github.com/ponsde/multi-agent-workflow/tree/main/skills/debug-duel
Command: npx skills add https://github.com/ponsde/multi-agent-workflow --skill debug-duel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and perform adversarial debugging tasks to identify bugs and audit opponent bug lists.

Core Features & Use Cases

  • Three-layer review framework: correctness, robustness, and engineering quality.
  • Round-based competition: Round 1 bug hunting; Round 2 opponent list reviews.
  • Self-verification and structured reporting to Leader.

Quick Start

Initiate a debug duel by selecting a Round 1 or Round 2 task and start the audit workflow.

Frequently Asked Questions about debug-duel

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

FAQPage Schema
What is an adversarial debugging workflow and how does it improve QA?

Adversarial debugging is a structured QA workflow where a Leader assigns rounds for independent bug discovery and opponent bug list evaluation. It enforces a three-layer framework—correctness, robustness, and engineering quality—to identify bugs through competition-style audits.

How do I start a bug hunting duel for code review?

To start a bug hunting duel, select a Round 1 task for independent bug discovery or a Round 2 task to evaluate an opponent's bug list. The workflow mandates strict self-verification of changes before acceptance and structured reporting to the Leader.

What does the three-layer review framework cover during an adversarial code audit?

The three-layer review framework covers correctness, robustness, and engineering quality. It is enforced during adversarial debugging duels to ensure comprehensive bug discovery and strict evaluation of an opponent's bug list before acceptance.

Can I use this adversarial debugging workflow to audit an opponent's bug list?

Yes, you can audit an opponent's bug list by selecting a Round 2 task. This evaluates the opponent's discovered bugs against the correctness, robustness, and engineering quality layers, requiring strict self-verification and structured reporting to the Leader.

Does the debug duel workflow require self-verification before accepting bug fixes?

Yes, the debug duel workflow mandates strict self-verification of changes before acceptance. This ensures all identified bugs and audited opponent bug lists meet the required correctness, robustness, and engineering quality standards during the QA competition.