> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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](/code-review/overview).

## The review flow

<div style={{ display: "grid", gridTemplateColumns: "repeat(3, 1fr)", gap: "1.5rem", marginTop: "1rem" }}>
  <div>
    <div style={{ display: "flex", alignItems: "center", gap: "8px", marginBottom: "10px" }}>
      <span style={{ display: "flex", alignItems: "center", justifyContent: "center", width: "22px", height: "22px", borderRadius: "50%", backgroundColor: "#7968FA", color: "#fff", fontSize: "0.75rem", fontWeight: 700, flexShrink: 0 }}>1</span>
      <h4 style={{ margin: 0, fontSize: "0.8rem", textTransform: "uppercase", letterSpacing: "0.05em", color: "#666" }}>Trigger</h4>
    </div>

    <p style={{ margin: 0 }}>Automatically when a PR is published, or on every push to it. <a href="/code-review/use-qodo-in-prs">Use Qodo in pull requests →</a></p>
  </div>

  <div>
    <div style={{ display: "flex", alignItems: "center", gap: "8px", marginBottom: "10px" }}>
      <span style={{ display: "flex", alignItems: "center", justifyContent: "center", width: "22px", height: "22px", borderRadius: "50%", backgroundColor: "#7968FA", color: "#fff", fontSize: "0.75rem", fontWeight: 700, flexShrink: 0 }}>2</span>
      <h4 style={{ margin: 0, fontSize: "0.8rem", textTransform: "uppercase", letterSpacing: "0.05em", color: "#666" }}>Understand</h4>
    </div>

    <p style={{ margin: 0 }}>Published directly on your pull request, every finding states what needs attention, why it matters, and how to fix it, ranked by severity. <a href="/code-review/comment-anatomy">Anatomy of a finding →</a></p>
  </div>

  <div>
    <div style={{ display: "flex", alignItems: "center", gap: "8px", marginBottom: "10px" }}>
      <span style={{ display: "flex", alignItems: "center", justifyContent: "center", width: "22px", height: "22px", borderRadius: "50%", backgroundColor: "#7968FA", color: "#fff", fontSize: "0.75rem", fontWeight: 700, flexShrink: 0 }}>3</span>
      <h4 style={{ margin: 0, fontSize: "0.8rem", textTransform: "uppercase", letterSpacing: "0.05em", color: "#666" }}>Act</h4>
    </div>

    <p style={{ margin: 0 }}>Discuss or dismiss a finding, or let Qodo apply the fix directly. <a href="/code-review/remediate-findings-in-prs">Remediate findings →</a></p>
  </div>
</div>

## 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.

<div style={{ display: "grid", gridTemplateColumns: "repeat(2, 1fr)", gap: "2rem", marginTop: "1rem" }}>
  <div>
    <h4 style={{ marginBottom: "6px" }}>Deepen your code review</h4>
    <p style={{ marginTop: 0, marginBottom: "10px" }}>Go beyond reading a finding, discuss it, fix it, or see the deeper issue behind it.</p>

    <ul style={{ paddingLeft: "1.1rem", margin: 0 }}>
      <li><a href="/code-review/chat-with-qodo-in-your-pull-requests">Chat with Qodo</a>: Ask follow-up questions or request changes, right in the thread.</li>
      <li><a href="/code-review/remediate-findings-in-prs">Remediate findings</a>: Let Qodo generate and apply the fix.</li>
      <li><a href="/code-review/commitable-code-suggestions">Commitable code suggestions</a>: Apply small fixes with one click.</li>
      <li><a href="/code-review/view-requirement-gaps-in-findings">Requirement gaps</a>: Catch PRs that miss their linked spec.</li>
      <li><a href="/code-review/view-ux-deviations-in-findings">UX deviations</a>: Catch drift from a linked Figma design.</li>
      <li><a href="/code-review/view-cross-repo-conflicts-in-findings">Cross-repository conflicts</a>: Catch breaking changes in related repositories.</li>
      <li><a href="/code-review/view-skill-related-findings">Skill-related findings</a>: Catch issues raised by your repository's own skills.</li>
    </ul>
  </div>

  <div>
    <h4 style={{ marginBottom: "6px" }}>Customize review output</h4>
    <p style={{ marginTop: 0, marginBottom: "10px" }}>Shape what Qodo shows you, where it shows up, and how much of it you see.</p>

    <ul style={{ paddingLeft: "1.1rem", margin: 0 }}>
      <li><a href="/code-review/pr-summary">PR summary</a>: Get a structured walkthrough of the change before you open a single file.</li>
      <li><a href="/code-review/reduce-review-noise">Reduce review noise</a>: Route findings by priority so only what matters stays visible.</li>
      <li><a href="/code-review/review-verbosity">Control review verbosity</a>: Determine how much detail each finding shows.</li>
      <li><a href="/code-review/comment-location">Comment location</a>: Select where the PR summary itself is posted.</li>
      <li><a href="/code-review/ignore-content-from-analysis">Ignore content from analysis</a>: Exclude files, branches, or PRs from review.</li>
      <li><a href="/code-review/feedback-location">Feedback location</a>: Define where findings are posted.</li>
      <li><a href="/code-review/findings-visibility">Findings visibility</a>: Control how many resolved findings stay visible.</li>
      <li><a href="/code-review/severity-thresholds">Severity thresholds</a>: Decide what counts as Action Required versus Informational.</li>
      <li><a href="/code-review/extra-instructions">Extra instructions</a>: Steer a review with your own guidelines.</li>
    </ul>
  </div>
</div>

## FAQ

<AccordionGroup>
  <Accordion title="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](/code-review/overview).
  </Accordion>

  <Accordion title="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](/code-review/overview).
  </Accordion>

  <Accordion title="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](/governance/review-standards) from your codebase, pull request history, and requirements, and every review agent applies them first. [Rule Miner](/governance/rule-enforcement/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.
  </Accordion>

  <Accordion title="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 [PR history in code reviews](/code-review/concepts/pr-history).
  </Accordion>

  <Accordion title="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](/governance/cross-repo-code-review).
  </Accordion>

  <Accordion title="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](/code-review/persistent-review-comments).
  </Accordion>

  <Accordion title="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](/code-review/commitable-code-suggestions) and [Remediate findings in pull requests](/code-review/remediate-findings-in-prs).
  </Accordion>
</AccordionGroup>