review tool scans the PR code changes, and generates a list of feedbacks about the PR, aiming to aid the reviewing process.
Note that the main purpose of the review tool is to provide the PR reviewer with useful feedbacks and insights. The PR author may prefer to focus on the output of the improve tool, which provides actionable code suggestions.
Example usage
Manual triggering
Run the tool manually by commenting/review on any PR:


How to use the review tool
Manual usage
Comment on the PR:
Learn more about automatic usage of tools.
review tool is:
review tool will run automatically on every PR, without any additional configurations. Edit this field to enable/disable the tool, or to change the configurations used.
Configuration options
Configuration options table
Configure thereview tool by setting configurations under the pr_reviewer part in your configuration file.
General options
| Possible configurations | Default value | What they do |
|---|---|---|
persistent_comment | true | If set to true, the review comment will be persistent, meaning that every new review request will edit the previous one. |
final_update_message | true | If set to true, updating a persistent review comment will automatically add a short comment to the PR with a link to the updated review. |
extra_instructions | none | Optional extra instructions for the tool. For example: “focus on the changes in the file X”, “Ignore changes in …” |
enable_help_text | true | If set to true, Qodo will display a help text in the comment. |
Enable\disable specific sub-sections
| Possible configurations | Default value | What they do |
|---|---|---|
require_score_review | false | If set to true, Qodo will add a section that scores the PR. |
require_tests_review | true | If set to true, Qodo will add a section that checks if the PR contains tests. |
require_estimate_effort_to_review | true | If set to true, Qodo will add a section that estimates the effort needed to review the PR. |
require_can_be_split_review | false | If set to true, Qodo will add a section that checks if the PR contains several themes, and can be split into smaller PRs. |
require_security_review | true | If set to true, Qodo will add a section that checks if the PR contains a possible security or vulnerability issue. |
require_ticket_analysis_review | true | If set to true, and the PR contains a GitHub or Jira ticket link, Qodo will add a section that checks if the PR fulfilled the ticket requirements. |
Adding PR labels
You can enable thereview tool to add specific labels to the PR:
| Possible configurations | Default value | What they do |
|---|---|---|
enable_review_labels_security | true | If set to true, Qodo will publish a possible security issue label if it detects a security issue. |
enable_review_labels_effort | true | If set to true, Qodo will publish a Review effort label, with a score from 1 to 5. |
Extra instructions
Extra instructions are important. Thereview tool can be configured with extra instructions, which can be used to guide Qodo to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples of extra instructions:
Labels
Thereview tool can auto-generate two specific types of labels for a PR:
- A
possible security issuelabel that detects if a possible security issue exists in the PR code (enable_review_labels_securityflag) - A
Review effort [1-5]: xlabel, where x is the estimated effort to review the PR (enable_review_labels_effortflag)