Auto Review
Last updated: October 2, 2026
Auto Review scans a page for the UI-quality issues a checklist misses: interactive states, forms, responsive gaps and dead UI. A local deterministic scan runs first, then an AI pass reviews a screenshot of the page to confirm the findings and add the ones only a human eye would normally catch. Findings become issues in your project with the screenshot and element attached. Auto Review runs in the Chrome extension, inside Team Review with no extension installed, and on a schedule through Scheduled Scans.
Start an Auto Review
- Open the OverlayQA sidebar on the page you want to review, or open the page in Team Review.
- Open the Workflows tab (or choose Run Workflows from a project view) and pick the Auto Review card: "Spot dead UI, broken states and gaps."
- Click Scan for UI issues.
The panel reports Scanning for UI issues... while the local checks run, then Refining with AI... while the AI pass reviews the page. Two chips in the header, Local scan and AI analysis, show which stage produced each finding, and Scan coverage and limits explains what the scan can and cannot see.
What Auto Review Checks
| Category | Examples of what it flags |
|---|---|
| Interactive states | Buttons and links without a hover, focus, or disabled state; controls that look clickable and do nothing. |
| Form quality | Fields without labels, missing required markers, validation that never fires. |
| Visual consistency | The same element styled differently across the page: spacing, color, or type that drifts. |
| Responsive gaps | Content that overflows, overlaps, or hides at narrower widths. |
| Dead UI | Links that lead nowhere and controls with no handler behind them. |
| Content quality | Leftover placeholder text, lorem ipsum, and unfinished copy. |
The dead-link check is a real probe: Auto Review clicks the control in a safe way and only reports it when nothing is listening, which keeps tracking pixels, broken images, and closed menus from being counted as bugs.
Reading the Results
A score header shows the Auto Review score as a percentage with a tier label such as Needs work. Below it, findings are grouped by category; use Filter Findings and Sort by in the toolbar to narrow the list, and Clear all to reset. Click a finding to expand it and see the element, the evidence, and which stage found it.
A clean page reports No UI issues found with the note "This page looks consistent. Re-scan after making changes." Click Re-scan after a fix to run the review again; a second run on a page you have reviewed before reports No new UI issues found when nothing changed.
Create Issues from Findings
- Tick the findings you want to keep, or use Select all at the top of the list (Deselect all clears it).
- Click Create issues, which shows the selected count. Each finding becomes an issue in your project with its screenshot, element, and category, and Creating... shows progress for large batches.
- Open the Actions menu for the rest: Copy findings, Copy as Markdown, or Copy as CSV to paste the findings into a message, a pull request, an AI coding tool, or a spreadsheet without a tracker; Ignore on this page or Ignore across project for findings you will not fix; or Export to a connected integration.
Single findings can be ignored from their detail card with the same two options. Ignored findings move to a dismissed list where Un-ignore or Restore brings one back, so a false positive never disappears for good.
Auto Review in Team Review and on a Schedule
In Team Review, Auto Review runs natively on any public URL from the workflows menu, with the same panel and the same issue creation. For pages you want watched over time, create a scheduled scan of type Auto Review; OverlayQA re-runs it on your cadence and emails you what changed.
Note: Auto Review is a page-level review, not a replacement for the Accessibility Audit or the Design System Audit. Run those for WCAG and token coverage; run Auto Review for the states, forms, and dead ends a checklist skips.
Frequently Asked Questions
Does Auto Review need Figma?
No. Auto Review reviews the live page on its own. Use Visual Comparison when you want to check the build against a Figma frame.
Why did a finding disappear after I fixed it?
Each scan is fresh. After a fix, a re-scan reports only what is still on the page, and a page with nothing new reports No new UI issues found. Issues you already created from earlier findings stay in your project.
Can I run Auto Review without installing anything?
Yes, on public URLs through Team Review in the dashboard. Localhost, staging behind a VPN, and login-gated pages need the Chrome extension, which runs the review in your own browser session.
What does the AI pass add?
The local scan checks the page deterministically. The AI pass reviews a screenshot of the full page to confirm those findings and add visual problems that rules cannot express, such as an element that is technically valid but reads as broken. Findings carry a Local scan or AI analysis chip so you can see which stage produced each one.