discussion-review

Orchestrates adversarial multi-agent code reviews using named background agents and a shared whiteboard.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/kai-kou/gem-hunter --skill discussion-review-kai-kou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discussion-review
Source: https://github.com/kai-kou/gem-hunter/tree/main/.claude/skills/discussion-review
Command: npx skills add https://github.com/kai-kou/gem-hunter --skill discussion-review-kai-kou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-pass code reviews often miss counterexamples, false claims, and edge cases because one reviewer cannot challenge its own assumptions. This Skill runs a structured adversarial review where multiple named agents independently analyze targets, rebut each other's findings across rounds, and converge on a verified verdict. ## Core Features & Use Cases - Multi-round adversarial debate: Round 1 collects independent analyses as claims; later rounds force participants to rebut or concede each other's specific points via a shared whiteboard (claim/rebuttal/consensus/verdict). - Dedicated counterexample and fact-check lenses: Assigns a participant to break proposed detection logic with concrete inputs, and requires fact-checkers to verify behavior across states and cross-check claims against embedded screenshots. - Guardrails and fallback: Handles unresponsive participants, circuit-breaker stops, and silent-free fallback to a legacy subprocess runner or fan-out evaluation, with post-hoc detection of unauthorized edits by participants. - Use Case: When reviewing a new quality-gate script, launch a discussion where one agent designs the logic, another crafts counterexample inputs that defeat it, and a fact-checker validates state-dependent behavior, producing a verdict JSON listing only issues that survived cross-examination. ## Quick Start Ask the AI to run a discussion review by forming a specialist team to debate and review the specified target files using the discussion-review workflow.

Frequently Asked Questions about discussion-review

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

FAQPage Schema
How do I run an adversarial multi-agent code review?▼

Provide a spec JSON with topic, brief, participants (name, model, lens), and a verdict schema, plus target paths. The orchestrator launches each participant as a named background agent for round 1 independent analysis, then uses SendMessage to start rebuttal rounds before posting a consensus and verdict.

What is the shared whiteboard used for in agent discussions?▼

The whiteboard, managed by discussion_whiteboard.py, is the single source of truth for the debate. Participants post claims, rebuttals, and concessions via the post command rather than editing files directly, and the lead posts consensus and verdict entries that are git-committed as a permanent record.

When should I use discussion review instead of fan-out evaluation?▼

Use discussion review when findings need cross-examination, such as validating detection logic or fact-checking claims, since rebuttal rounds filter out false positives. Use fan-out for lightweight tasks where independent evaluations simply need aggregation without debate.

What happens if a participant agent does not respond?▼

If one participant's completion notice never arrives while others finish, the lead sends a single SendMessage status check. If there is still no response, that participant is treated as absent, the review proceeds, and the absence is recorded in the verdict.

Does the skill have a fallback if native agent orchestration fails?▼

Yes. If native execution fails twice in a row or agents cannot be launched, it falls back to the legacy run_discussion_review.py subprocess path, logging the reason. If that also fails, it degrades to a fan-out of independent parallel evaluations.