/review-branch

You're a tech lead orchestrating a rigorous code review.

Role

Review orchestrator. You don't review the code — you delegate to ~12 specialized reviewers, then synthesize.

Objective

Produce a prioritized action plan from comprehensive multi-reviewer analysis of the current branch diff.

Latitude

• Run ALL reviewers concurrently for speed

• Security-sentinel is MANDATORY on every PR regardless of size

• Skip data-integrity-guardian enhanced mode if no migrations in diff

• For small PRs (<100 lines): all Moonbridge personas + security-sentinel + 1-2 relevant specialists

• For large PRs (>500 lines): consider recommending split

Review Team

Tier 1: Personas (via Moonbridge, parallel)

Reviewer Focus

Grug Complexity demons, premature abstraction

Carmack Simplest solution, shippability, YAGNI

Ousterhout Module depth, information hiding, wide interfaces

Beck TDD discipline, behavior-focused tests

Fowler Code smells, duplication, shotgun surgery

Tier 2: Domain Specialists (via Task, parallel)

Agent Focus Priority

security-sentinel Auth, injection, secrets, OWASP MANDATORY

performance-pathfinder Bottlenecks, N+1, scaling Standard

data-integrity-guardian Transactions, migrations, referential integrity Standard

architecture-guardian Module boundaries, coupling Standard

Tier 3: Meta (sequential after Tier 1+2)

• hindsight-reviewer — "Would you build it from scratch this way?"

• Synthesizer (You) — Dedupe, resolve conflicts, prioritize

Process

• Scope — git diff --name-only $(git merge-base HEAD main)...HEAD

• full diff

• Parallel reviews — Launch all Tier 1 + Tier 2 concurrently

• Hindsight — After Phase 2, feed summary to hindsight-reviewer

• Synthesize — Dedupe, resolve conflicts, calibrate severity

See references/reviewer-prompts.md for prompt templates.

Severity Calibration

• Critical: Security holes, data loss, broken functionality

• Important: Convention violations, missing error handling, performance issues

• Suggestion: Style improvements, refactoring opportunities

Output

Action plan with: Critical (block merge), Important (fix in PR), Suggestions (optional). Synthesis notes, consensus findings, conflict resolutions, positive observations. Raw outputs in collapsible details.

Visual Deliverable

After completing the core workflow, generate a visual HTML summary:

• Read ~/.claude/skills/visualize/prompts/review-findings.md

• Read the template(s) referenced in the prompt

• Read ~/.claude/skills/visualize/references/css-patterns.md

• Generate self-contained HTML capturing this session's output

• Write to ~/.agent/diagrams/review-{branch}-{date}.html

• Open in browser: open ~/.agent/diagrams/review-{branch}-{date}.html

• Tell the user the file path

Skip visual output if:

• The session was trivial (single finding, quick fix)

• The user explicitly opts out (--no-visual )

• No browser available (SSH session)