6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。

MITAuto-check passedDevOps & Cloud

Install Review Team

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill review-team -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins review-team --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/s977043/river-review/skills/agent-skills/review-team .claude/skills/review-team && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-team
GitHub stars
1.3k
Token cost
~1.7k tokens
SKILL.md length
236 words
Files
1
Skills in repo
716
Repo updated
First seen
Licence
MIT

At a glance

6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。

  • Works in 5 steps: consensus 指摘を最優先で確認する —… → multi 指摘を次に確認する — 2ロールが合意した指摘 → blindSpots を見て追加実行を検討する —… → …
  • A major release needs exhaustive multi-angle review
  • SKILL.md covers When to Use / いつ使うか, Reviewer Roles / レビュアーロール, Execution Flow / 実行フロー and Output Fields / 出力フィールド, plus 4 more sections
  • Calls npm and npx

What it does

Review Team is an agent skill from hashgraph-online/awesome-codex-plugins. 6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。 Parallel multi-role review with consensus scoring (consensusLevel) and Tech Lead report. Use when a major release needs exhaustive multi-angle review, or when a single-perspective review is not enough and you want confidence that no reviewer angle was missed(重要リリース前の網羅レビュー・多視点の確証が 欲しいとき)。

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.

When your agent uses it

  • A major release needs exhaustive multi-angle review
  • A single-perspective review is not enough and you want confidence that no reviewer angle was missed(重要リリース前の網羅レビュー・多視点の確証が 欲しいとき)

Example prompts

  • “/review-team”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. consensus 指摘を最優先で確認する — 複数の独立したロールが同箇所を指摘したため信頼度が最も高い
  2. multi 指摘を次に確認する — 2ロールが合意した指摘
  3. blindSpots を見て追加実行を検討する — 未実行ロールが多い場合はそのロールを追加して再実行
  4. single 指摘はノイズ混入の可能性がある — ロール固有の観点からの指摘なので文脈に応じて判断
  5. scope で対応範囲を切り分ける — in-diff は本 PR が追加行で持ち込んだ問題、pre-existing は変更ファイル内だが追加行の外にある既存コードへの指摘。pre-existing は文脈参考として扱い、本 PR…

What it can do on your machine

Read from SKILL.md and the folder at commit 3e1456a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Team loads about 1.7k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 236 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 3e1456a, republished under its MIT licence (© hashgraph-online). 236 words, ~1,672 tokens.

Download SKILL.mdSave it as .claude/skills/review-team/SKILL.md (or your agent's skills folder).
name
review-team
description
6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。 Parallel multi-role review with consensus scoring (consensusLevel) and Tech Lead report. Use when a major release needs exhaustive multi-angle review, or when a single-perspective review is not enough and you want confidence that no reviewer angle was missed(重要リリース前の網羅レビュー・多視点の確証が 欲しいとき)。
id
review-team
phase
upstream, midstream, downstream
severity
major
applyTo
**/*
tags
entry, routing, multi-agent, parallel, consensus, team, orchestration
version
0.1.0
license
MIT

Review Team(レビュー・チーム)

複数の専門レビュアーロールを並列実行し、複数ロールが同一箇所を指摘した「コンセンサス指摘」を自動的に浮かび上がらせるレビュー手法。

When to Use / いつ使うか

  • 重要リリース前の網羅的なレビューが必要なとき
  • セキュリティ・バグ・テスト・依存関係を一度に確認したいとき
  • 「どこから見ても問題ない」という確証が欲しいとき
  • 単一視点のレビューでは不十分と感じるとき

Reviewer Roles / レビュアーロール

ロール担当領域自動選択条件(auto モード)
bug-hunterロジックエラー・境界値・null/undefined 参照・並行アクセス競合・エラー握り潰し常時
security-scannerインジェクション・認証・機密漏洩リスクファイルまたはインフラ変更
test-gapテストカバレッジ・エッジケーステストファイルまたはアプリファイル3件以上
dependency-reviewerサプライチェーン・バージョンジャンプpackage.json / lockfile 変更
frontend-reviewerアクセシビリティ・レンダリング・レスポンシブ・loading/error 状態の欠落.tsx/.jsx/.css/.scss/.sass/.less/.vue/.svelte 変更
ci-cd-reviewerワークフロー・アクションのピン・権限.github/workflows/ 変更
Stage / risk signal による選択(#1545 P1・任意)

auto モードは、上記のファイル種別ヒューリスティックに加えて、ホスト(PlanGate 等)が渡す 形式化された signal でもロールを選択できる。signal は任意で、渡さない場合の挙動は従来と不変(後方互換)。signal は既存ロールのみへ写像し、新ロールは作らない。写像先を持たない Lens(devex 等)は Reviewer Lens Taxonomy(Issue #1545)の Gap として記録され、レビュアーは追加しない。

signal 種別追加ロール
stage: plansecurity-scanner, test-gap
stage: designfrontend-reviewer
stage: exec / stage: releasesecurity-scanner
stage: verifytest-gap
touchesAuth / changesPermissions / handlesSensitiveDatasecurity-scanner
databaseMigration / breakingChangesecurity-scanner
changesUi / changesUserFlowfrontend-reviewer
deploymentChangeci-cd-reviewer

選択理由(selectionReasons)と required / skipped の状態は run 結果の autoSelection に記録される。bug-hunter は常に required、選択されなかったロールは skipped に入る。

実装 SSoT: src/lib/reviewer-orchestrator.mjs の selectRolesAuto / computeAutoSelection。本表と実装は二重管理のため、片方を変更したら同一 PR で両方を整合させる。

Execution Flow / 実行フロー

text
Step 1: ロール決定
  ├─ 明示指定あり → 指定ロールを使用
  └─ 指定なし → auto(差分内容から最適ロールを自動選択)

Step 2: 並列実行
  [bug-hunter] [security-scanner] [test-gap] ...(同時起動)
       ↓
  Union-Find クラスタリングで重複 finding を統合

Step 3: consensusLevel の付与(finding ごと)
  agreement.length ≥ 3 → "consensus" ★★★
  agreement.length = 2  → "multi"     ★★
  agreement.length ≤ 1  → "single"    ★

Step 4: Tech Lead レポートの生成(追加 LLM コストなし)
  top3Findings    : consensusLevel → severity → scope 順の上位3件
                    (consensusLevel が severity に優先する。severity は
                      consensusLevel が同値のときだけ効き、scope は上位2キーが
                      同値のときだけ in-diff を先に置く)
  blindSpots      : 今回実行されなかったロール一覧
  consensusSummary: consensus / multi / single の件数集計

Output Fields / 出力フィールド

finding ごと
json
{
  "title": "SQLインジェクションの可能性",
  "severity": "critical",
  "consensusLevel": "consensus",
  "agreement": ["bug-hunter", "security-scanner", "test-gap"],
  "reviewerRole": "bug-hunter",
  "scope": "in-diff"
}
teamLeadReport(run 全体)
json
{
  "teamLeadReport": {
    "top3Findings": [...],
    "blindSpots": [{ "role": "frontend-reviewer", "label": "Frontend Reviewer" }],
    "consensusSummary": { "consensus": 1, "multi": 3, "single": 8, "total": 12 }
  }
}

How to Run / 実行方法

River Review は npm パッケージを公開しない(プロジェクト方針)。したがって npx river-review は使えない。実行環境ごとに次の手段を使う。

プラグイン / エージェント環境(第一手段・CLI 不要)

Claude Code / Codex のプラグイン経由では、エージェントがこのスキルの手順を直接実行する。CLI は不要で、上記の Execution Flow(ロール決定 → 並列実行 → consensusLevel 付与 → Tech Lead レポート)をエージェント自身が再現する。

  • スラッシュコマンド: /review-team または /review-team bug-hunter,security-scanner
  • CLI が無くても設計どおり動作する。CLI 実行を試みて失敗しても、スキル駆動のレビューで継続すること。
コントリビューター(リポジトリ内)

リポジトリ内では river CLI をアクセラレータとして使える(任意)。

bash
# 差分から自動選択(推奨)
npm run river -- run . --reviewers auto

# ロールを明示指定
npm run river -- run . --reviewers bug-hunter,security-scanner,test-gap

# JSON 出力(teamLeadReport を含む)
npm run river -- run . --reviewers auto --output json

# コスト事前確認
npm run river -- run . --reviewers auto --dry-run

CLI は必須でない。存在しない、または失敗した場合はスキル駆動のレビューで継続する。

GitHub Actions

Actions では CLI が実行エンジンとして起動される。ワークフロー設定は Actions 用ドキュメントを参照する。

Output Interpretation / 結果の読み方

  1. consensus 指摘を最優先で確認する — 複数の独立したロールが同箇所を指摘したため信頼度が最も高い
  2. multi 指摘を次に確認する — 2ロールが合意した指摘
  3. blindSpots を見て追加実行を検討する — 未実行ロールが多い場合はそのロールを追加して再実行
  4. single 指摘はノイズ混入の可能性がある — ロール固有の観点からの指摘なので文脈に応じて判断
  5. scope で対応範囲を切り分ける — in-diff は本 PR が追加行で持ち込んだ問題、pre-existing は変更ファイル内だが追加行の外にある既存コードへの指摘。pre-existing は文脈参考として扱い、本 PR のスコープを超えた修正を招かないようにする。値が無い場合は fail-safe で in-diff 扱いになる

Cost / コスト

  • 実行ロール数 × 通常レビューコストが目安
  • auto モードは差分に関係するロールのみを起動するため無駄がない
  • Tech Lead レポートは追加 LLM コストなし(deterministic 計算)

他スキルとの関係

スキル関係
adversarial-review補完: adversarial は「どう壊れるか」に特化。review-team は「網羅的な多視点」に特化
river-review上位: river-review entry skill がロールを決定し review-team を起動する経路もある

© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/s977043/river-review/skills/agent-skills/review-team of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 3e1456a

Compare with similar skills

Review Team next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Team compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Team this skillhashgraph-online/awesome-codex-plugins1.3k—~1.7kAutomated safety check: PassMIT
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Thesvgglincker/thesvg2.8k—~1.5kAutomated safety check: PassMIT
UI Architectopenobserve/openobserve22k—~16kAutomated safety check: NotesAGPL-3.0
Winui AppLanceMcCarthy/DevOpsExamples1721 repos~2.8kAutomated safety check: PassApache-2.0
Borg Live Debugkaranhudia/borg-ui1.7k—~1.4kAutomated safety check: NotesAGPL-3.0

Similar skills

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed
  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated today
    DevOps & CloudAuto-check passed
  • UI Architect

    openobserve/openobserve

    ALWAYS use this skill for ANY change to the OpenObserve web UI (web/) — even a single-line UI modification.

    22k GitHub stars~16k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Winui App

    LanceMcCarthy/DevOpsExamples

    Bootstrap, develop, and design modern WinUI 3 desktop applications with C and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and…

    172 GitHub starsUsed in 1 repo~2.8k tokens
    DevOps & CloudAuto-check passed
  • Borg Live Debug

    karanhudia/borg-ui

    Live Borg debugging by exec-ing into the borg-web-ui Docker container.

    1.7k GitHub stars~1.4k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Convex Self Hosting

    waynesutton/markdown-site

    Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time.

    627 GitHub stars~1.4k tokensUpdated 4 mo ago
    DevOps & CloudAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 716 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Questions about Review Team

What does Review Team do?

6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。. Review Team is an agent skill from hashgraph-online/awesome-codex-plugins. 6つの専門レビュアーロールを並列実行し、consensusLevel(複数ロールの合意度)と Tech Lead レポート(top3指摘・blindSpots・consensusSummary)で結果を統合する マルチエージェントレビュー entry skill。 Parallel multi-role review with consensus scoring (consensusLevel) and Tech Lead report.

When should I use Review Team?

Review Team fits situations like: A major release needs exhaustive multi-angle review; A single-perspective review is not enough and you want confidence that no reviewer angle was missed(重要リリース前の網羅レビュー・多視点の確証が 欲しいとき).

How do I install Review Team in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill review-team -a claude-code`. Or copy the skill folder (plugins/s977043/river-review/skills/agent-skills/review-team in hashgraph-online/awesome-codex-plugins) into .claude/skills/review-team in your project. Claude Code loads it when a task matches its description.

How do I install Review Team in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill review-team -a codex`. Or copy the skill folder (plugins/s977043/river-review/skills/agent-skills/review-team in hashgraph-online/awesome-codex-plugins) into .agents/skills/review-team in your project. Codex loads it when a task matches its description.

Can I use Review Team in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill review-team -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-team, .gemini/skills/review-team, .github/skills/review-team and .opencode/skills/review-team in your project.

What does Review Team need to run?

Going by SKILL.md and its folder, Review Team needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.

Does Review Team access the network?

SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Review Team safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Team use?

Review Team is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Team use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Review Team?

Skills that share tags, products or a category with Review Team: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Thesvg (glincker/thesvg, 2.8k stars), UI Architect (openobserve/openobserve, 22k stars) and Winui App (LanceMcCarthy/DevOpsExamples, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Team?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,267 GitHub stars. The repository holds 716 skills in this directory. The repository was last updated on October 10, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.