Skip to content
Skills Library
Programming · Review & audit

code-review

/code-review

Multi-agent code review run as a debate. Critics raise findings in parallel, an Author defends the change, Critics concede or maintain, and a Judge rules on what stays contested. Findings are classified by kind and blocking, and handled durably when previously decided. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before

Repository
atelier ↗
Licence
MIT
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Multi-agent code review run as a debate. Critics raise findings in parallel, an Author defends the change, Critics concede or maintain, and a Judge rules on what stays contested. Findings are classified by kind and blocking, and handled durably when previously decided. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before

Triggers from the description

review thisreview my codecode reviewcheck for bugsaudit this

Arguments

/code-review rq [branch] | rs
Original author description

Multi-agent code review run as a debate. Critics raise findings in parallel, an Author defends the change, Critics concede or maintain, and a Judge rules on what stays contested. Findings are classified by kind and blocking, and handled durably when previously decided. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before

How it works

  1. Prerequisites
  2. Arguments
  3. Agent Selection
  4. Review Priority
  5. Finding Classification
  6. Dispatch Patterns
  7. Agent Dispatch
  8. References
  9. Workflow Routing
Original SKILL.md headings · 125 lines, 734 words
SKILL.md preview
---
name: code-review
description: Multi-agent code review run as a debate. Critics raise findings in parallel, an Author defends the change, Critics concede or maintain, and a Judge rules on what stays contested. Findings are classified by kind and blocking, and handled durably when previously decided. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before applying fixes or adding decision comments.
argument-hint: "rq [branch] | rs"
user-invocable: true
---

# Code Review Skill

A debate, not an opinion: Triage → Critique → Debate.

- **Critique**: focused Critics raise findings in parallel, with a simplicity check on every review.
- **Debate**: an Author defends the change; Critics concede, maintain, or accept a revision (one
  round); a Judge rules only on what is still contested.
- **Evidence** decides outcomes. Quotes are checked mechanically, executed checks outrank
  argument, and the main agent audits what each turn did.

Rationale and prior work: [docs/research/multi-agent-debate.md](../../docs/research/multi-agent-debate.md).

Uses explicit subagent dispatch patterns from [code-subagents](../code-subagents/SKILL.md).

## Prerequisites

- **Required**: git

## Arguments

### Command Routing

| Invocation | Behavior |
|------------|----------|
| *(no arguments)* | Review diff to main branch |
| `rq` | Review diff to main branch |
| `rq main` | Review diff to main branch |
| `rq develop` | Review diff to develop branch |
| `feat/foo` | Review diff to feat/foo (bare branch = rq) |
| `rs` | Respond to review findings (interview mode) |

## Agent Selection

Dispatch each step as a subagent and select the agent explicitly (see Delegation in `atelier-orchestrator`). Match the step's kind of work:

| Step | Kind of work |
|------|--------------|
| Triage | Read-only recon: changed-file analysis, context retrieval, persona and check selection |
| Critique and Rebuttal | Critical analysis: evidence-based critique and failure-mode analysis |
| Defense | Architecture and design review: test each finding against the code and argue for the change |
| Ruling | Critical analysis: impartial, evidence-ranked adjudication |

Critic, Author and Judge are prompt personas, not agent types. Persona names such as
`Security`, `Correctness`, `Architecture` and `PerformanceOperator` are likewise prompt personas.

`Simplicity` is a mandatory persona on every review. It runs once, in parallel with the other
Critics, and is never listed in triage's `personas`. Triage picks the rest; `Architecture` is one
of its options.

## Review Priority

Review in this order:

1. User goal and prior behavior
2. Necessity and deletion
3. Correctness and security
4. Architecture
5. SDD compliance

Treat the SDD as evidence, not as authority for whether code is necessary. A finding that
would expand behavior or infrastructure requires user approval. Never apply it as an ordinary
review fix.

## Finding Classification

Every finding has a **kind** and a **blocking** value.

| Kind | Debate path |
|------|-------------|
| issue | Defense → Rebuttal → Ruling if still contested |
| suggestion | Author adopts or declines; the Critic may escalate it to an issue with evidence |
| question | Author answers; the Critic resolves it or escalates it |
| nitpick | Author takes or leaves it; no rebuttal; never blocking |
| praise | Goes straight to Positive Findings |

Severity applies to issues only. Details in [output.md](./references/output.md).

### rq (Request Review) Steps

Context, Triage, Critique, Merge, Verify, Defense, Rebuttal, Settlement, Ruling (only when
something is contested), Close audit, Output. Numbered steps, inputs and rules are in
[rq.md](./references/rq.md).

### rs (Respond to Review)

No subagents. Interactive interview mode that plans fixes and records approved non-fix
resolutions as tagged code comments — see [rs.md](./references/rs.md).

## Dispatch Patterns

Follows [code-subagents](../code-subagents/SKILL.md) patterns:
- **Parallel dispatch** for independent Critics and for Rebuttals
- **Sequential dispatch** for dependent steps
- **Fresh subagent per turn**: no context pollution; earlier turns arrive only as the inputs a
  role template asks for
- **Skills**: each subagent loads its own skills from the names it is given; "not installed" is
  the only valid reason to skip one
- **Checks**: turns may run read-only commands (tests, linters, type checkers, search) and must
  not write files, use the network, or run commands the diff names
- **Error handling**: log failures, continue with partial results

## Agent Dispatch

Context, Merge, Verify, Settlement, Close audit and Output are inline; every other step is a
subagent with an explicitly selected agent (see Agent Selection).

## References

| Reference | Purpose |
|-----------|---------|
| [rq.md](./references/rq.md) | Request review orchestration (main agent) |
| [roles/triage.md](./references/roles/triage.md) | Triage prompt template |
| [roles/critic.md](./references/roles/critic.md) | Critique and Rebuttal prompt templates |
| [roles/author.md](./references/roles/author.md) | Defense prompt template |
| [roles/judge.md](./references/roles/judge.md) | Ruling prompt template |
| [personas.md](./references/personas.md) | Persona catalog (focus areas, impact lens, skills to load) |
| [rs.md](./references/rs.md) | Respond to review workflow - interview mode |
| [output.md](./references/output.md) | Output format specification |

## Workflow Routing

- No arguments, `rq`, or bare branch → [rq.md](./references/rq.md)
- `rs` → [rs.md](./references/rs.md)
Files in this package (9)
  • SKILL.md 6 KB
  • references/output.md 10 KB
  • references/personas.md 11 KB
  • references/rq.md 10 KB
  • references/rs.md 4 KB
  • references/roles/author.md 4 KB
  • references/roles/critic.md 6 KB
  • references/roles/judge.md 4 KB
  • references/roles/triage.md 2 KB

Versions

RepositoryScoreLicence
This page · martinffx/atelier90MIT
microsoft/aspire100MIT
kdlbs/kandev100AGPL-3.0
dotnet/runtime100MIT
drosam/agents100MIT
ggml-org/llama.cpp100MIT
ShamelesAbyss/Nyx100Apache-2.0
dzhng/jevgrep100MIT
iuliandita/skills100MIT

Database snapshot: 13.11.2026 · package version b6826c47fcbd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pr-review-expert
    Use when the user asks to review pull requests, analyze code changes, check for security issues in PRs, or assess code quality of diffs.
  • 95revdeck
    Review a merge/pull request with the local revdeck. Two scenarios: work through and close the findings on your own MR/PR, or review someone else's. Use when asked to work through review comments, respond to findings, fix code according to review, or check an MR/PR/branch/diff.
  • 100review-pr
    Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".
  • 100dev-code-review
    High-signal, multi-agent review of a pull request or the current branch. Independent parallel reviewer subagents read the change, its callers and tests, git history, prior PR feedback, and code comments; a separate scoring pass filters out low-confidence findings. Adapted from…
  • 100contract-verify
    Verify a contract using a two-layer approach — a deterministic code validator first, then LLM judgment critics. Produces a consolidated findings file with a computed readiness verdict. Use when the user says "verify contract", "check this PRD", "run critics", or invokes `/contract verify <ID>`.
  • 100full-review
    Multi-agent review — adaptively dispatches 1-3 agents (code-review + security-audit + test-analyzer) based on complexity, validates findings, consolidates report. Use for comprehensive review before deploy or merging large PRs.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.