Ordered by fit for the question above, not by size. Each entry says what the tool is best at.
Rams
Editorial choice
Best for UI, design and accessibility in pull requests
Rams reviews the design quality of UI code: React, Vue, Svelte, Angular, React Native, SwiftUI and HTML/CSS. It checks 365 rules across accessibility, color, typography, spacing, components, UX, motion and craft, scores each pull request from 0 to 100 and leaves one-click fix suggestions in about a minute. It also runs as an MCP server, so Claude Code, Cursor, Codex and ChatGPT can check UI while they write it. Free on one public repository, paid plans from $39 a month.
Try Rams
CodeRabbit
Best for general line-by-line pull request review
CodeRabbit comments on each pull request with a summary and line-level suggestions across logic, style and common mistakes. It works across the major Git hosts and suits teams that want broad coverage of every change.
CodeRabbit website
Greptile
Best for review with full codebase context
Greptile indexes the whole repository, so its comments can point to how a change affects code elsewhere. It suits larger codebases where a diff alone hides the real risk.
Greptile website
GitHub Copilot code review
Best for teams already paying for Copilot
Copilot can be requested as a reviewer on a pull request inside GitHub. It needs no new vendor and suits teams that want a first pass without adding another tool.
GitHub Copilot code review website
Cursor Bugbot
Best for catching bugs in Cursor-heavy teams
Bugbot reviews pull requests for likely bugs and links back into the Cursor editor to fix them. It suits teams that already write most of their code in Cursor.
Cursor Bugbot website
Qodo
Best for an open source review agent
Qodo makes PR-Agent, an open source pull request reviewer, alongside a hosted product with test generation. It suits teams that want to run and adjust the reviewer themselves.
Qodo website