Review Deep - Parallel Multi-Agent Code Review

VerifiedSafe

Deep code review using 4 parallel specialized agents for comprehensive analysis of quality, security, and testing.

Sby Skills Guide Bot
DevelopmentAdvanced
307/23/2026
Claude Code
#code-review#multi-agent#parallel-review#security#quality

Recommended for

Our review

Conducts a deep code review by dispatching four parallel specialized agents (code quality, security, test quality, and architectural consequences) and consolidates findings into a structured report.

Strengths

  • Covers four distinct review dimensions simultaneously
  • Identifies conflicting opinions between reviewers
  • Produces a structured report with severity classification

Limitations

  • Requires high context length and may be resource-intensive
  • May produce conflicting recommendations that need manual resolution
  • Dependent on the quality of each individual agent's analysis
When to use it

Use for large or critical pull requests where thorough review is needed across multiple dimensions.

When not to use it

Avoid for small, simple changes where a single-pass review is sufficient.

Security analysis

Safe
Quality score92/100

The skill orchestrates a code review using read-only tools (Read, Grep, Glob) and git diff via Bash, dispatching analysis agents that do not perform any destructive or exfiltrating actions. No risky operations are present.

No concerns found

Examples

Review a specific file
/review-deep src/component.ts
Review current changes
/review-deep
Review a directory
/review-deep src/

name: review-deep description: Code review paralelo com múltiplos agentes especializados. argument-hint: "[arquivo ou diretório]" user-invocable: true allowed-tools: Read, Grep, Glob, Bash, Agent model: opus effort: high context: fork

Review Deep — Code Review Paralelo Multi-Agente

Review profundo com 4 revisores paralelos: $ARGUMENTS

Escopo

Se argumento fornecido

Revisar: $ARGUMENTS

Se nenhum argumento

git diff --name-only HEAD
git diff --cached --name-only

Processo

Fase 1 — Preparação

  1. Identificar arquivos a revisar
  2. Ler cada arquivo para entender contexto
  3. Montar briefing: arquivos, propósito, stack

Fase 2 — Dispatch paralelo (4 agentes)

Despachar TODOS em paralelo:

Revisor 1 — Code Quality (backend/frontend)

  • Correção lógica, edge cases, tipos
  • Legibilidade, naming, SRP, dead code
  • Padrões do projeto

Revisor 2 — Security (security)

  • OWASP Top 10, input validation, injection
  • Secrets, auth, headers, deps vulneráveis

Revisor 3 — Test Quality (backend/frontend)

  • Cobertura: happy path + edge cases
  • Nomes descritivos, AAA, mocks vs integração

Revisor 4 — Consequences (architect)

  • Impacto em dependentes
  • Breaking changes não documentados
  • Efeitos cascata, compatibilidade

Fase 3 — Consolidação

  1. Coletar findings dos 4 revisores
  2. Remover duplicatas
  3. Marcar conflitos: "⚠️ Conflito" se revisores discordam
  4. Classificar por severidade

Fase 4 — Relatório

## Review Deep — Relatório Consolidado

### Revisores
| Revisor | Findings | Críticos | Importantes |
|---------|----------|----------|-------------|

### 🔴 Crítico (bloqueia merge)
- **[Revisor]** [arquivo:linha] Descrição
  - Impacto: [...]
  - Fix: [...]

### 🟡 Importante (deve corrigir)
### 🔵 Sugestão

### ⚠️ Conflitos entre revisores
- [Revisor A] diz X vs [Revisor B] diz Y

### ✅ Pontos positivos

## Veredicto: PASS | FAIL | NEEDS DISCUSSION
**Confiança: X/5**

Quando usar

  • /review = 1 pass sequencial, rápido, mudanças pequenas
  • /review-deep = 4 agentes paralelos, PRs grandes ou críticos
Related skills