Review code independently with five AI models, combine their reports, and filter out duplicate or unsupported findings. Present concrete bugs and risks for approval, then fix only the issues the user accepts.
Run five independent max-effort reviews (Fable 5.1, Opus 5.5, GPT-6 Astra, GPT-6.1 Sol, Muse Wonder), merge their findings, and fix only what the user approves. Manual only: run when a human types /total-review; agents must never invoke it on their own.
Review the instructions the agent will receive before you install.
Five reviewers, each in its own Cloudroom thread: the two best models from Anthropic and from OpenAI, plus Meta's Muse Wonder, all at their highest effort and in full permission mode (the harness maximum). Never swap or downgrade a model, effort, or permission mode. If one is unavailable, stop and tell the user.
Always spawn with --permission-mode full. That is Claude Code's bypass permissions (--dangerously-skip-permissions) and Codex's YOLO mode (no approvals, danger-full-access sandbox). A child cannot exceed its parent, so if this thread is not in full mode, stop and tell the user.
--provider claude-code --model claude-fable-5-1--provider claude-code --model 'claude-opus-5-5[1m]'--provider codex --model gpt-6-astra--provider codex --model gpt-6.1-sol--provider pi --model openrouter/meta/muse-wonder (Pi harness, OpenRouter). Only OpenRouter offers max for Muse; never use the vercel-ai-gateway route.max in supportedReasoningEfforts: room-cli provider models claude-code --json, room-cli provider models codex --json, and room-cli provider models pi --json.--reasoning-level max --permission-mode full --title "Total review: <model>":
room-cli thread spawn --parent-self --project "<project ID>" --environment <env ID from room-cli status --json>cloudroom thread spawn (see cloudroom thread --help).bb thread spawn (see /bb-cli).thread show that each thread runs the right model at its effort in full permission mode.Send all five the same neutral brief: scope, paths, intended behavior, and diff/base revision.
Ask for a thorough senior-developer review, including related code and tests. Review only; change no files. Report serious or critical issues with file and line, a fix, and merge readiness. Separate verified findings from guesses. Use plain English.
Never hint at suspected bugs, mention the other reviewers, or share one reviewer's output with another.
Run thread wait, then thread output, on each. Idle status, timeouts, and queued retries are not completion. Report a failed reviewer; never pass off partial output as a review.
Read all five reports in full. Deduplicate. Keep only real bugs and risks; drop style preferences, theoretical edge cases, and non-issues. Agreement alone does not prove an issue is real.
Show the user:
[fable], [opus], [astra], [sol], [muse]. Most-reported first.Share full reports only if the user asks.
Only after the user approves: fix the approved issues, then commit and push with the standard ship workflow.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Work through sixteen open questions in four rounds to clarify major product decisions, risky changes, or large refactors. The agent adapts later questions to earlier answers, then turns your decisions into a step-by-step implementation plan.
Document approved decisions as concise ADRs, or architecture decision records. It preserves the user's meaning and conditions, removes conversational filler, follows the project's numbering, and presents the saved record for review.
Keep a Mac awake for a chosen duration or while a specified process runs. The skill uses built-in macOS tools to manage one session, verify that sleep prevention is active, and control whether the display stays on.
Turn a feature or refactoring idea into a concise implementation prompt for another agent. It asks focused questions one at a time, records decisions, and includes development steps, validation, and working rules.
Inspect and manage BB threads, environments, projects, and plugins through its command line interface. The skill guides agents to identify the correct targets, apply changes, and verify the resulting state.
Create, install, and debug TypeScript plugins that extend bb with custom pages, sidebar panels, CLI commands, agent tools, themes, and other features. The skill also guides development reloads, log checks, and verification of installed plugins.