SkillAgentSearch skills...

total-review

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. Use for /total-review, or when the user or another agent asks for a total review.

Install / Use

npx skills add davidondrej/skills --skill total-review

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Universal

Our assessment of total-review

total-review scores 84/100 on our quality scale, 637th of 950 AI & Machine Learning skills we index.

Its SKILL.md is 3.6 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.

With 4,079 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so total-review is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found 2 patterns worth reviewing before you install total-review. An AI review judged it risky: The skill explicitly instructs spawning child review threads with `--permission-mode full`, equating it to Claude Code's `--dangerously-skip-permissions` and Codex YOLO mode, which disables approval prompts.

  • mediumDisables the agent's permission promptsline 12
    …full`. That is Claude Code's bypass permissions (`--dangerously-skip-permissions`) and Codex's YOLO mode (no approvals, `danger-full-access`…
  • mediumDisables the agent's permission promptsline 12
    …ns (`--dangerously-skip-permissions`) and Codex's YOLO mode (no approvals, `danger-full-access` sandbox). A child cannot exceed its parent, …

AI review: risky

  • The skill explicitly instructs spawning child review threads with `--permission-mode full`, equating it to Claude Code's `--dangerously-skip-permissions` and Codex YOLO mode, which disables approval prompts.
  • It mandates this bypass unconditionally ('Always spawn with...') and tells the agent to stop if it cannot use full permission mode.
  • While the overall purpose (multi-model code review) is legitimate, disabling permission prompts weakens the agent's safeguards, which matches the 'risky' definition.

AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

total-review compared with similar skills

All 4 of these similar skills score higher than total-review; compare them before choosing.

SkillScoreStarsUpdatedFormat
total-review (this skill)by davidondrej844.1k53d agoSKILL.md
claude-memby thedotmack100117.6ktodayCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
CowAgentby zhayujie10048.0ktodayCLAUDE.md

Frequently asked questions

How do I install total-review?
Run npx skills add davidondrej/skills --skill total-review. The install tabs above show the steps for each supported agent.
Which AI agents does total-review work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is total-review safe to use?
Our scan of the whole file found 2 patterns worth reviewing before you install total-review. An AI review judged it risky: The skill explicitly instructs spawning child review threads with --permission-mode full, equating it to Claude Code's --dangerously-skip-permissions and Codex YOLO mode, which disables approval prompts. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is total-review still maintained?
The repository was last updated about 2 months ago, so total-review is actively maintained.

name: total-review description: '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. Use for /total-review, or when the user or another agent asks for a total review.'

Total Review

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.

Permissions

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.

Reviewers

  • Fable 5.1: --provider claude-code --model claude-fable-5-1
  • Opus 5.5 (1M): --provider claude-code --model 'claude-opus-5-5[1m]'
  • GPT-6 Astra: --provider codex --model gpt-6-astra
  • GPT-6.1 Sol: --provider codex --model gpt-6.1-sol
  • Muse Wonder: --provider pi --model openrouter/meta/muse-wonder (Pi harness, OpenRouter). Only OpenRouter offers max for Muse; never use the vercel-ai-gateway route.

1. Launch

  1. Confirm each model is listed with max in supportedReasoningEfforts: room-cli provider models claude-code --json, room-cli provider models codex --json, and room-cli provider models pi --json.
  2. Spawn all five in parallel, one thread each, with the reviewer flags plus --reasoning-level max --permission-mode full --title "Total review: <model>":
    • Local thread: room-cli thread spawn --parent-self --project "$ROOM_PROJECT_ID" --environment <env ID from room-cli status --json>
    • Cloud thread: cloudroom thread spawn (see cloudroom thread --help).
    • Fallback only: bb thread spawn (see /bb-cli).
  3. Confirm with thread show that each thread runs the right model at its effort in full permission mode.

2. Brief

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.

Include this sentence in the brief, word for word: "During your final answer, Rate each issue you find from 1 to 10 on how often it would happen, and 1-10 on how bad it would be"

Never hint at suspected bugs, mention the other reviewers, or share one reviewer's output with another.

3. Collect

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.

4. Merge and report

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:

  • A numbered list, one line per issue: what + where.
  • Tags for who found it: [fable], [opus], [astra], [sol], [muse]. Most-reported first.
  • One line: how many findings were dropped.
  • Ask: approve these fixes, or adjust the list?

Share full reports only if the user asks.

5. Fix and ship

Only after the user approves: fix the approved issues, then commit and push with the standard ship workflow.

Related Skills

View on GitHub
GitHub Stars4.1k
CategoryAI
Updated1mo ago
Forks601

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions