Skip to main content
Qodo reviews the full codebase, not just the diff, to generate a structured summary of the pull request (PR) that gives reviewers meaningful context before they look at a single line of code. The summary captures the intent of the change, estimates how long the review will take, surfaces high-level suggestions, and diagrams the architecture where relevant.
Generated PR summary comment showing tags, the Walkthroughs section, and File Changes grouped by category
The summary includes:
  • Summary, tags, and time estimate: A brief summary of the PR’s intent, followed by tags (Bug fix, Tests, Enhancement, Documentation, or Configuration changes) and a time estimate, so reviewers can prioritize before opening a single file.
  • Walkthroughs: A Description, Diagram, and High-Level Assessment that break down what changed, how, and why.
  • File Changes: Modified files grouped by category, for a quick view of the change surface.
Code review file changes overview showing modified file paths, change types, and lines added or removed
For more information, see Comment anatomy.

​
Generate a PR summary manually

Comment on the pull request: /agentic_describe Qodo acknowledges the request and posts the generated summary directly in the pull request.

​
Generate a PR summary automatically

Qodo generates a summary automatically when a pull request is opened or updated. This is the default behavior. If you want to change the default behavior, use one of the following methods.
  1. Log in to the Qodo portal.
  2. Navigate to Configurations > Workflow > PR summary.
  3. Set PR summary trigger to Manual only (generated using /agentic_describe) or Published PRs (generated automatically when a PR is published, default).
For more information, see Configure Qodo using the portal.

​
Disable automatic PR summaries in .pr_agent.toml

Automatic PR summaries run when /agentic_describe is included in pr_commands. Remove it from the list to disable automatic summaries and rely on manual requests only.
pr_commands is set per Git provider section, or in [config] as a fallback for providers that don’t define their own. For more information, see Configuration and command reference.

​
Set the location of the summary in the pull request

By default, Qodo posts the PR summary as a standalone comment and does not modify the pull request description. To publish it in the pull request description instead, or let Qodo choose dynamically, see Comment location.

​
Publish the review time estimate as a native label or tag

GitHubGitLabAzure DevOps
As pull request volume grows, seeing the review effort directly in your Git provider’s pull request list makes it easier to compare and triage which reviews to tackle first, without opening each one.
GitHub pull request list showing review time estimate labels such as "Less than 10 minutes" and "10-20 Minutes" next to each pull request title
  1. Log in to the Qodo portal.
  2. Navigate to Configurations > Workflow > PR summary.
  3. Enable Publish review time estimate label.
Qodo then applies the review time estimate as a native pull request tag (Azure DevOps) or label (GitHub, GitLab), in addition to the estimate already displayed inside the summary. It’s visible on the pull request and in the pull request list (for example, “10-20 Minutes”), without opening the summary. Disabled by default.

​
Configure the review time estimate label in .pr_agent.toml

Default: false.