The Qodo Code Review experience

Qodo brings multi-agent, context-aware code review directly into your pull requests, catching breaking changes, spec gaps, and design deviations that diff-only tools miss.

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. See how the review experience works.

NewCross-repo code review·Review effort mode·Chat with Qodo

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.

• Chat with Qodo: Ask follow-up questions or request changes, right in the thread.
• Remediate findings: Let Qodo generate and apply the fix.
• Commitable code suggestions: Apply small fixes with one click.
• Requirement gaps: Catch PRs that miss their linked spec.
• UX deviations: Catch drift from a linked Figma design.
• Cross-repository conflicts: Catch breaking changes in related repositories.
• Skill-related findings: Catch issues raised by your repository’s own skills.

Customize review output

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

• Review effort mode: Match review depth to the risk of each change automatically, or set a fixed mode.
• PR summary: Get a structured walkthrough of the change before you open a single file.
• Reduce review noise: Route findings by priority so only what matters stays visible.
• Control review verbosity: Determine how much detail each finding shows.
• Comment location: Select where the PR summary itself is posted.
• Ignore content from analysis: Exclude files, branches, or PRs from review.
• Feedback location: Define where findings are posted.
• Findings visibility: Control how many resolved findings stay visible.
• Severity thresholds: Decide what counts as Action Required versus Informational.
• Extra instructions: Steer a review with your own guidelines.

FAQ

Does Qodo only look at the diff, or the whole repository?

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. See How Qodo code review works.

What does Qodo's multi-agent review actually do?

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. See How Qodo code review works.

Does Qodo know our team's own coding standards, or does it just apply generic best practices?

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.

Does Qodo learn from my team's past review decisions?

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. See Understanding PR history indexing.

Can Qodo see changes in a related repository when reviewing my PR?

Yes, with cross-repository code review. Define a relationship between repositories and Qodo traces impact in both directions, for example flagging a PR that breaks a data model or API contract owned by another repository. See Cross-repository code review.

Can Qodo re-check a PR automatically on every new commit, not just when it's published?

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. See Persistent review comments.

Can Qodo apply a fix, not just flag the issue?

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. See Commit code fixes directly in the pull request and Remediate findings in pull requests.