Running subagents across harnesses: a five-part independent code review workflow

PawelHuryn · x · 2026-11-21

Pawel Huryn shares his full setup for coordinating coding subagents across harnesses: Claude Code (Opus 5.5 at xhigh) coordinates and handles small fixes, Codex on GPT-6.2 Sol builds bigger changes, and every review runs in a fresh session—never reusing the thread that built the code.

His five-part reviewer brief, in order: (1) what the product is in two sentences; (2) the change straight from git, never a written summary; (3) who uses what, how often, and what's serious even when rare; (4) "what would block or break this release?" with each finding labeled INTRODUCED or PRE-EXISTING plus exact repro steps; (5) a ranked list of claim, file:line, and fix.

Key discipline: no earlier findings, suspected files, or "do you approve?"—ask a reviewer if it approves and it approves. Claude Code verifies every finding against the code before fixes. Both skills (codex-agents, independent-review) are open-sourced free.

Related event: Developer Shares Multi-Agent Review Workflow and Open-Sources 45 Agent Skills(2 posts)→

Original post →

More from coding & agent

coding & agent channel →