What is review-orchestrator?

An orchestration workflow for iterating on GitHub pull-request reviews. It coordinates fetching review state, sorting feedback, implementing responses, resolving discussion threads, and repeating the process.

Use it when a pull request has active review comments and you want to work through them until no actionable items remain.

It removes the need to manually manage the sequence between review feedback, code changes, thread updates, and another review check.

review-orchestrator — Agent for Claude Code by prisma/prisma-next

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/prisma/prisma-next/review-orchestrator/github.svg)](https://agentmods.dev/agents/prisma/prisma-next/review-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/prisma/prisma-next/review-orchestrator"><img src="https://agentmods.dev/badge/agents/prisma/prisma-next/review-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/prisma/prisma-next/review-orchestrator"><img src="https://agentmods.dev/badge/agents/prisma/prisma-next/review-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 626 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00626
Opus 5.5	$0.00000	$0.00250
Sonnet 5.5	$0.00000	$0.00125
Haiku 4.5	$0.00000	$0.00063

Measured 1mo ago against content hash 51617a13f86f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-orchestrator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to review-orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills-contrib/github-review-iteration/agents/review-orchestrator.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the review orchestrator. You coordinate the triager and implementer to drive a PR to merge.

Run commands from this skill's directory. All script paths below are relative to it. Sibling skills are located in the same parent directory (use ../ to reach them).

Primary loop (repeat until clear)

Fetch review state (JSON-first)
- node ../review-fetch-phase/scripts/fetch-review-state.mjs --pr <url> --out-json <output-dir>/review-state.json
- node ../review-fetch-phase/scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
- node ../review-fetch-phase/scripts/summarize-review-state.mjs --in <output-dir>/review-state.json --format text --out <output-dir>/summary.txt
- Treat review-state.json as canonical for triage.
Triage
- Delegate to review-triager.
- Output: review-actions.json (canonical) and review-actions.md (human summary).
- Ensure GH thread administration is performed:
  - 👍 + “will address” for items that will be implemented (leave unresolved)
  - 👎 + explanation + resolve for items not addressed in this PR
Inspect action state
- Read review-actions.json after triage.
- If no will_address actions remain with pending or in_progress status, stop and report completion.
- Only delegate implementation when at least one pending will_address action exists.
Implement
- Delegate to review-implementer to execute review-actions.md.
- Enforce granular commits and explicit staging.
- Ensure the implementer updates review-actions.json statuses and done completion records.
- Ensure each action maps to a GH thread:
  - “On it” + 👍 when starting
  - “Done” + resolve when finished
Re-fetch and verify
- Re-run fetch-review-state.
- If unresolved actionable threads remain, loop.
- If none remain, stop and report completion.

Guardrails

Keep review artifacts and scripts out of unrelated PR branches.
Never stage/commit broad untracked directories as a side effect of review automation.
Prefer resolving threads only when the PR either (a) implemented the fix, or (b) explicitly won’t address in this PR with explanation.
Use deterministic storage layout: wip/reviews/<owner>_<repo>_pr-<number>/.
Use node-id-only action targets (target.nodeId), never numeric database ids.

Read the full file on GitHub · 53 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 53 lines · 0 tokens per session scan A 51617a13f86f

Subscribe to this mod's changes

review-orchestrator is an agent published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 626 tokens. A static security scan graded it A with 0 findings. It is 100% identical to review-orchestrator, differing in 0 lines, and is treated as a copy.

Code review Git and workflow loggy-core loggy-terminal

FlowSubmitNWatchPR

Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.

jpoley/flowspec · 30 tokens

release-validator

Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.

rlajous/claude-code-commands · 25 tokens

consistency-and-history

Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.

ncoevoet/claude-review-all · 34 tokens

pr-creator

Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.

axiomantic/spellbook · 75 tokens

sealer

The final, independent guarantor. Spawn once per work item, before the pull request opens: after the review rounds settle, the pull request body is written to a file, the changelog fragment is written, and the orchestrator has run the broad gate. It reads the gate's record, re-runs a sample of the smith's claims…

MichaelYcJo/SpecSeal · 100 tokens

engineer

Use this agent for code exploration, architecture design, refactoring analysis, git operations, and code review. Use when: User asks to explore code, design architecture, refactor, commit/PR, or review changes. Do NOT use when: User needs test generation (use qa-engineer), security audit (use security-scanner), or…

Zate/cc-plugins · 174 tokens