What is parallel-review?

A French-language workflow for reviewing a pull request or code component from several angles using specialist subagents. It chooses reviewers for security, tests, Kubernetes operations, documentation, and public content based on the files involved.

Use it to review pull requests or component paths, assess test coverage, inspect security and Kubernetes changes, and review documentation or public content. It can run up to four specialist reviews in parallel.

It organizes checks that might otherwise be missed when reviewing a change from only one perspective. It also loads the relevant pull-request or component context before assigning reviewers.

How stoa-platform/stoa configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to stoa-platform/stoa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/stoa-platform/stoa/main/.claude/skills/parallel-review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/stoa-platform/stoa

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/skills/stoa-platform/stoa/parallel-review/github.svg)](https://agentmods.dev/skills/stoa-platform/stoa/parallel-review)

Your own site

<a href="https://agentmods.dev/skills/stoa-platform/stoa/parallel-review"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/parallel-review/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/skills/stoa-platform/stoa/parallel-review"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/parallel-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 926 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 original No closer match found 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.00040	$0.00926
Opus 5.5	$0.00016	$0.00370
Sonnet 5.5	$0.00008	$0.00185
Haiku 4.5	$0.00004	$0.00093

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

Security

Grade A, and why

parallel-review 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 2mo 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.

.claude/skills/parallel-review/SKILL.md · 106 lines

How it starts

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

Parallel Review — Review multi-angle orchestree

Executer une review parallele complete sur: $ARGUMENTS

Workflow

Step 1: Charger le contexte

Si c'est un numero de PR:

gh pr view $0
gh pr diff $0 --name-only
gh pr checks $0

Si c'est un chemin de composant:

git diff main --name-only -- $0

Step 2: Determiner les reviewers necessaires

Fichiers modifies	Subagent a lancer
`.py`, `.tsx`, `.ts`, `.rs` (code applicatif)	security-reviewer (toujours)
`.test.`, `test_`, `.spec.*`	test-writer (evaluer couverture)
Tout code sans tests correspondants	test-writer (identifier les manques)
`Dockerfile`, `k8s/`, `.yaml` (k8s), `nginx`, `charts/`	k8s-ops
`docs/`, `*.md`, `CLAUDE.md`, `memory.md`	docs-writer
`docs/.md`, `blog/`, `.astro` (contenu public)	content-reviewer

Minimum: security-reviewer est TOUJOURS lance. Maximum: 4 subagents en parallele (budget tokens).

Step 3: Deleguer aux subagents

Lancer les subagents en parallele via le Task tool:

security-reviewer: "Analyse de securite des changements de la PR $0"
test-writer: "Evaluer la couverture de tests pour les fichiers modifies dans la PR $0. Identifier les tests manquants."
k8s-ops (si applicable): "Valider les changements infra/k8s de la PR $0 contre la checklist k8s-deploy.md"
content-reviewer (si contenu public): "Audit conformite du contenu public de la PR $0 contre content-compliance.md"

Step 4: Synthetiser les resultats

Combiner les rapports des subagents en un rapport unifie:

## Review Parallele: $ARGUMENTS

### Date: [date]
### Branche: [branch]
### Fichiers modifies: [count]

---

### Securite (security-reviewer)
**Verdict**: Go / Fix / Refaire
[Resume des findings]

### Tests (test-writer)
**Verdict**: Go / Fix / Refaire
[Resume: couverture actuelle, tests manquants]

### Deployment (k8s-ops)
**Verdict**: Go / Fix / Refaire / N/A
[Resume ou "Pas de changements infra detectes"]

### Conformite Contenu (content-reviewer)
**Verdict**: Go / Fix / Refaire / N/A
[Resume: concurrents, clients, prix, reglementations, disclaimers — ou "Pas de contenu public modifie"]

---

### Verdict global: **Go** / **Fix** / **Refaire**

### Actions requises
1. [Action specifique avec fichier et ligne]
2. ...

### Actions suggerees (non-bloquantes)
1. ...

Read the full file on GitHub · 106 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.

2mo ago First seen · 106 lines · 40 tokens per session scan A 331c7b120013

Subscribe to this mod's changes

parallel-review is a skill published in the GitHub repository stoa-platform/stoa (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 926 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review LLM ai api-management claude enterprise gateway

parallel-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
parallel-reviewstoa-platform/stoa	Skill	9	yesterday	Apache-2.0	A	40	Claude Code
lyrikgebruder/wirken	Skill	194	2d ago	MIT	A	15	Claude Code
librariangebruder/wirken	Skill	194	2d ago	MIT	A	34	Claude Code
notesgebruder/wirken	Skill	194	2d ago	MIT	A	10	Claude Code
tdx-assetsgebruder/wirken	Skill	194	2d ago	MIT	A	58	Claude Code
aggregatorgebruder/wirken	Skill	194	2d ago	MIT	A	30	Claude Code
githubgebruder/wirken	Skill	194	2d ago	MIT	A	9	Claude Code

stoa: Skill for Claude Code