arXiv:2610.10961v1 Announce Type: cross Abstract: Coding agents increasingly share a workstation while drawing on separate providers and subscription allowances. A second agent can inspect a completed answer, but the call spends another pool and may provide no substantive finding. We describe an advisory cross-provider review contract: distinct resource pools, bounded execution, restricted reviewer capabilities, complete input delivery, usable semantic output, explicit failure states and durable per-attempt evidence. In a controlled, agent-authored pilot of 20 paired development turns, eight had a material reviewer finding (95% exact interval 19.1-63.9%). A boundary-condition scan across both reviewer backends reproduced a previously discovered false success on partial input: four truncation levels passed historically and failed after repair. The scan also found and repaired cancellation during process reaping. In real CLI probes, Claude had no writing tools; Codex attempted writes in five of five read-only trials, each write tool failed, and no disposable repository changed. These tests cover specified paths and versions, not field reliability. A preregistered shadow study of metadata-only review allocation accrued 25 formal observations before an exact-runtime regression found a third defect: a reviewer exiting nonzero with a well-formed verdict was counted as complete. Exit status was not recorded per attempt, so exposure cannot be resolved retrospectively. The 25 formal and two pending records remain an audit cohort; the measurement-valid cohort restarted at zero and collection has begun. No gate result is reported.
- When the user is requested as reviewer, read the PR diff and description.
- Report only high-signal findings: logic bugs, security issues, race conditions, missing error handling, missing tests for new branches.
- Rank findings by severit…
Analyze this codebase's architecture: 1. Evaluate the overall structure and patterns 2. Identify potential architectural issues 3. Suggest improvements for scalability 4. Note areas that follow best practices Focus on maintainability and mo…
---
agent: 'agent'
description: 'Perform a comprehensive code review'
---
## Role
You're a senior software engineer conducting a thorough code review. Provide constructive, actionable feedback.
## Review Areas
Analyze the selected code fo…
Tell it to analyze the codebase for the need of refactoring regarding the guidelines. Tell it to only plan, no coding. Let it write down the plan in a doc. Let another chat review the plan. Update the plan. You can let the different chats d…