The Qodo Code Review experience - Qodo Documentation
Skip to main content
Most review tools only look at the diff. Qodo reviews every pull request (PR) with specialized AI agents that understand your full repository, history, and standards. For more information, see how the review experience works.

​
The review flow

1

​
Trigger

Automatically when a PR is published, or on every push to it. Trigger a code review →

2

​
Understand

Published directly on your pull request, every finding states what needs attention, why it matters, and how to fix it, ranked by severity. Anatomy of a finding →

3

​
Act

Discuss or dismiss a finding, or let Qodo apply the fix directly. Remediate findings →

​
Explore Qodo’s capabilities

Beyond the core review, Qodo covers the rest of the pull request lifecycle, from deeper interaction with findings to tuning exactly what gets reviewed and how.

​
Deepen your code review

Go beyond reading a finding, discuss it, fix it, or see the deeper issue behind it.

​
Customize review output

Shape what Qodo shows you, where it shows up, and how much of it you see.

​
FAQ

Qodo analyzes the full repository, not just the changed lines, so it can reference files outside the diff and reason about changes the way a principal engineer would. For more information, see How Qodo code review works.
Specialized agents evaluate the change in parallel, correctness, standards compliance, architecture, and risk, then a judge agent merges their findings, removes duplicates, and filters out anything low-confidence before it reaches the pull request. For more information, see How Qodo code review works.
Both, in priority order. Qodo builds Review Standards from your codebase, pull request history, and requirements, and every review agent applies them first. Rule Miner continuously turns recurring patterns from your team’s own PR history into new enforced rules, so standards keep evolving with how your team actually works. Where nothing team-specific applies, Qodo falls back to established best practices.
Yes. Qodo uses your pull request history to judge whether a finding is likely to matter, prioritizing issues similar to ones your team has fixed before and quieting ones you’ve consistently dismissed. For more information, see Understanding PR history indexing.
Yes. Turn on the Per commit trigger in the Qodo portal, or set handle_push_trigger = true in .pr_agent.toml, and Qodo updates the same review comment as new commits land. For more information, see Enable persistent review comments.
Yes. Small, single-file fixes get a one-click Apply Suggestion button; larger fixes come with an Agent prompt you can hand to an AI coding tool to implement with full context. For more information, see Commit code fixes directly in the pull request and Remediate findings in pull requests.