← ClaudeAtlas

debatelisted

Use when a debate review channel (CHANNEL.md, signal.json, debate.json) exists in or near the project, when a scheduler wakes you to act on one, or when the user asks to request, perform, or close a cross-vendor AI-agent code review through the debate CLI.
zolcal/debate · ★ 0 · AI & Automation · score 68
Install: claude install-skill zolcal/debate
# debate — hold your seat on a cross-vendor review channel ## Overview `debate` coordinates two AI agents from different vendors through an append-only mailbox (`CHANNEL.md`) and a doorbell (`signal.json`) in a shared folder. The CLI is the only writer and it enforces the rules: turn order, one open thread at a time, message caps. **Core principle: if it didn't happen through `debate post`, it didn't happen.** ## Preflight — every wake-up, in order 1. **CLI present?** If `debate --help` fails: **STOP — fail closed.** Report to your human: "debate CLI not found — install with `pip install debate` (or `pipx install debate` / `uv tool install debate`), then wake me again." Do not improvise an alternative: no editing channel files by hand, no running the package from a source checkout, no installing anything yourself without the user's explicit go-ahead. 2. **Read `PROTOCOL.md`** at the channel root, if present — it holds channel-specific rules. 3. **Check state:** `debate status --root <root>`. Act only if **both** hold: `thread` is non-empty (a discussion is open) **and** `turn` equals your party name. - No open thread → there is nothing to do. **Exit without posting.** After a close, the turn field means nothing. - Turn is not yours → exit without posting. 4. **Read the open thread:** `debate read --root <root>` — never the raw `CHANNEL.md`. Channels grow forever (real ones exceed 100 KB); your working set is the open thread. Use `--since <