Every agent-authored pull request now gets a second opinion
A second agent can now review every pull request an agent opens for correctness and conventions before it reaches you, not just pass automated checks.
Summary
Agent-authored pull requests used to arrive with passing checks and nothing else — whether the change actually did what was asked was still something you had to work out by reading the diff yourself. A second agent can now review every pull request automatically before it reaches you.
What You Gain
Passing checks tell you the code runs; they don't tell you it did the right thing. Reviewing every agent-authored change yourself, line by line, is exactly the kind of work automation should take off your plate — while still giving you a real opinion to rely on, not just a green checkmark.
Set a review agent on a project, and every pull request from that project's tasks is reviewed automatically: does it do what was asked, is it correct, does it follow your project's own conventions. The verdict and reasoning appear directly on the pull request, with findings posted as comments — and if changes are requested, the original agent picks them up, fixes them, and triggers a fresh review on its own.
How It Works
- Choose a review agent per project; every pull request from that project's tasks is reviewed automatically.
- A pull request only shows as ready to merge once the review approves the exact current version of the code — pushing new changes requires a fresh approval.
- Requested changes go straight back to the authoring agent, which fixes them and resubmits; this loop is capped, so a persistent disagreement between agents lands in your Decisions list instead of looping indefinitely.
- A reviewer never reviews its own work, and always reviews the exact pull request it was asked to, so the verdict always matches what's actually being merged.
- You can always take over and review a pull request yourself instead, falling back to automated checks alone.
Where to Find It
Set a review agent from a project's settings — available now on every project. One honest limit: this controls the readiness signal inside Effigate Command Center; the actual merge button on GitHub is still yours to press.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.