Review agent-written code changes before merge, focusing on concrete correctness defects. Uses independent subagent reviews, targeted verification, and fresh checks after substantial repairs, with a deeper evidence-based process for security, concurrency, persistence, or data-loss risks.
Review agent-written changes before merge, after substantial edits, or when re-reviewing a repair. Use the adversarial protocol for high-risk changes or an explicitly requested deep review.
Review the instructions the agent will receive before you install.
Review to reduce developer attention. Surface concrete correctness defects; suppress style, nits and speculative improvements unless requested.
Use subagents in the current runtime, not a second model or external review service as a gate. Keep review read-only until an authorized repair. Do not commit review receipts, scratch reproductions or generated logs.
For implementation handoff or merge, read dogfood and merge
for per-change verification, first-pass completion, re-dogfood and merge receipts.
The main agent owns dogfood, mergeability, the merge and every pushed fix.
A PR merges when an independent review subagent passes it and it causes no red
of its own; base reds, flakes and pending checks don't hold it. Don't wait for a
person. Ship risky user-visible behavior behind a setting or Debug toggle and fix
a bad default in the next nightly. main is nightly: stack fixes, do not revert.
For security, persistence, concurrency, data-loss risks, or a requested deep review, use the full protocol:
These stages retain the advanced evidence protocol; ordinary reviews use the short default pass above.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Organize cmux windows, workspaces, and split panes so an agent can target the right terminal reliably. Create terminals with startup commands, move or reorder panels, change focus, and flash a panel to identify it.
Guide substantial Swift changes in cmux with rules for package boundaries, dependency direction, state management, concurrency, and API documentation. Structure code so public package types can be tested without launching the app.
Guide cmux backend changes with consistent rules for Effect, a TypeScript library for structured error handling. Covers Cloud VM state, database migrations, provider integrations, and authentication and payment checks so changes follow the intended architecture.
Maintain cmux billing code with guidance on Stripe checkout, pricing, subscriptions, and access rights. It maps the relevant services and provides workflows for testing purchases, handling payment events, and rolling out billing changes.
Automate browsing in cmux panels without taking focus away from current work. Target a specific panel to open pages, fill forms, click controls, wait for page changes, extract content, and inspect download history.
Capture cmux windows as screenshots or video clips from the CLI. Create visual evidence for pull requests and bug reports, with region selection and captions to explain drags, animations, or layout changes.