Home→Glossary→Automated Review

Automated Review

Automated Review

A separate agent pass checking a diff before a human ever sees it

✓ Runtime & Session
Talk to AY Automate ↗
A separate pass, not self-reviewRuns before the human reviewerCatches the obvious, not a substitute for judgment

What is an Automated Review

Automated review is using a separate agent pass, distinct from the one that actually wrote the code, to check a diff for bugs, security issues, or style problems before it ever reaches a human reviewer. The separation matters: the agent that just wrote something is poorly positioned to catch its own blind spots, a fresh pass with no investment in the original approach looks at the same diff differently.

This works well for the kind of issue a checklist can catch: an obvious security mistake, a missed edge case, a style convention the project always follows, a pattern that looks like the exact bug that caused a past incident. It is a real filter, catching a meaningful share of issues before a human ever has to spend time on them.

It is not a substitute for a human reviewer, it is a pass that runs before one, meant to reduce how much of a human's attention gets spent on things a systematic check could have caught. Judgment calls about whether an approach was the right one in the first place still land with a person, automated review narrows what reaches them, it does not replace the review itself.

AY Automate

Build your own agent skills, not just prompts.

We design, build, and ship the Claude Code skill libraries production teams actually run on.

Talk to AY Automate ↗

Key properties

✓Performed by a different agent pass than the one that wrote the code
✓Runs before the diff reaches a human, not instead of a human
✓Best at catching obvious issues, not replacing real judgment