AI Agent
Agent Resumption
Fixes a pull request that failed review without starting the work over, and without repeating the same rejected fix twice.
What is it?
An agent that reads the branch as it currently exists, not as a continuation of a previous attempt, audits whether the blocker was missing evidence or an actual code defect since those need completely different fixes, and reconciles format before touching content so the review agent doesn't fail it again for the same superficial reason.
What does it do?
- -Diagnoses before it fixes: an evidence gap and a code defect are treated as different problems requiring different responses, not the same "try again" loop.
- -Format-matching before content: if a PR description's evidence section doesn't match what the task now requires, it gets rewritten to match first, closing the most common repeat-failure loop.
- -Re-enters review automatically: a fixed branch flows straight back into the Review agent, no manual re-trigger.
- -Capped, not infinite: each task gets a bounded number of attempts before it needs a human, so retries can't loop forever silently.
Why does it matter?
A failed review is data, not just a stop sign. A naive retry that ignores why it failed will often produce the exact same failure again.
Who is it for?
Engineering Leaders
How it works
Claude Sonnet, reading the current branch state plus every existing PR comment, running the same evidence-audit-first protocol before writing a single line of code.