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

# Qodo's daily tips

> Qodo appends a rotating tip to every pull request (PR) summary comment, each one a way to discover and take full advantage of Qodo's code review capabilities. This page collects them all in one place, instead of waiting for each one to appear on a PR.

<Frame>
  <img src="https://mintcdn.com/qodo/qet38I6bUuVSeTsr/images/code-review/pr-summary-tip-of-the-day.png?fit=max&auto=format&n=qet38I6bUuVSeTsr&q=85&s=b779ec294d1622bb8d63c780e953eb53" alt="Tip of the day section in a pull request summary comment, with links to more tips, customizing Qodo, and the Qodo docs" width="834" height="201" data-path="images/code-review/pr-summary-tip-of-the-day.png" />
</Frame>

<Note>
  To stop seeing daily tips in your code review, disable **Show tip of the day** under **Comment parts** on the [Display](https://app.qodo.ai/configurations?tab=display) tab in your Qodo portal.
</Note>

<AccordionGroup>
  <Accordion title="One click from a finding straight to the rule or relationship that caused it" icon="lightbulb">
    Open a finding's Evidence section to jump directly to the source. Rule violations link to the rule on the **Rules** page, and cross-repo conflicts link to the relationship that caused them. Use these links to check or fix the underlying cause.

    See [Anatomy of a Qodo Code Review](/code-review/comment-anatomy#unpack-a-code-review-finding) for the full guide.
  </Accordion>

  <Accordion title="Too many rules firing? Choose exactly which repos Qodo imports rules and skills from" icon="lightbulb">
    Click **Import rules and skills**, then select only the Git organizations or repositories whose standards matter to your team. Qodo imports rules and skills from those sources alone, so findings stay focused and noise-free.

    See [Importing rules and skills](/governance/rule-enforcement/building-review-standards#importing-rules-and-skills) for the full guide.
  </Accordion>

  <Accordion title="Hide resolved findings to focus on what still needs action" icon="lightbulb">
    By default, findings you fix stay in the review comment, struck through. To keep the comment focused on open findings, navigate to **Configurations** > **Display** > **Resolved findings** and move resolved findings to a separate Resolved findings section, or turn off **Show resolved findings** to hide them entirely.

    See [Track resolved findings](/code-review/track-resolved-findings).
  </Accordion>

  <Accordion title="Pick a display mode instead of tweaking every Display option by hand" icon="lightbulb">
    Choose Lean, Balanced, Robust, or Custom from the display mode selector to instantly shape how much detail Qodo surfaces in your reviews. No need to toggle each Display setting one by one.

    See [Configure Qodo using the portal](/configuration/display#display-modes) for the full guide.
  </Accordion>

  <Accordion title="See how risky a PR is at a glance with blast radius labels" icon="lightbulb">
    Qodo scores each pull request as Large, Medium, or Small blast radius based on the scope and sensitivity of the change, and posts it as a native PR label so you can triage review effort straight from the PR list.

    See [Assess code change risk using blast radius](/code-review/assess-risk-with-blast-radius) for the full guide.
  </Accordion>

  <Accordion title="Chat with Qodo about any finding by starting a comment with 'qodo' or '@qodo'" icon="lightbulb">
    Start any PR comment, review comment, or inline code comment with `qodo`, `@qodo`, or `/qodo`, or open with a greeting like `Hey qodo`, to chat with Qodo about a finding. Ask it to explain the issue, discuss the suggestion, or ask follow-up questions in natural language. Qodo only responds when addressed, so reviewer discussions are never interrupted.

    See [Chat with Qodo in your pull requests](/code-review/chat-with-qodo-in-your-pull-requests) for the full guide.
  </Accordion>

  <Accordion title="Disagree with a finding? Ask Qodo to dismiss it, with your reason on record" icon="lightbulb">
    Tell Qodo to dismiss a finding and explain why. The finding is struck through and marked as Dismissed in the review comment, so the rest of the team sees the decision.

    See [Chat with Qodo in your pull requests](/code-review/chat-with-qodo-in-your-pull-requests) for the full guide.
  </Accordion>

  <Accordion title="Push back, ask questions, or dig deeper by replying 'qodo' on any finding" icon="lightbulb">
    Reply to any finding to push back on a suggestion, request a deeper explanation, or refine the recommendation. Your feedback shapes the conversation on the PR.

    See [Chat with Qodo in your pull requests](/code-review/chat-with-qodo-in-your-pull-requests) for the full guide.
  </Accordion>

  <Accordion title="Choose which labels appear on a finding, and whether they show icons or text" icon="lightbulb">
    **Displayed labels** controls which labels appear on each finding (severity, finding type, finding category, relevance), and **Label style** controls whether they show as icon and text or icon only. Find both in the portal under **Configurations > Display > Labels**, which has a live preview of your review comment.

    See [Configure Qodo using the portal](/configuration/display#labels) for the full guide.
  </Accordion>

  <Accordion title="Enable the Remediation agent and Qodo fixes findings in a dedicated fix PR" icon="lightbulb">
    Under **Configurations > Remediation**, turn on the Remediation agent and Qodo fixes review findings for you, delivered as a dedicated fix PR or pushed directly to your source branch. Set an auto-fix severity threshold to control which findings it picks up.

    See [Remediate findings in your pull request](/code-review/remediate-findings-in-prs) for the full guide.
  </Accordion>

  <Accordion title="Land a fix right on your PR by typing 'qodo, fix this' on a finding" icon="lightbulb">
    Type `qodo, fix the null pointer issue in this PR` and the chat agent applies the fix without you leaving the PR. This is best for targeted fixes where you want control over what changes.

    See [Remediate findings in your pull request](/code-review/remediate-findings-in-prs) for the full guide.
  </Accordion>

  <Accordion title="Describe a rule in plain language on the Rules page and Qodo drafts it for you" icon="lightbulb">
    On the **Rules** page in the portal, describe the rule you want in plain language, such as "Restrict console.log in prod builds", and Qodo drafts it for you, complete with examples and severity.

    See [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules) for the full guide.
  </Accordion>

  <Accordion title="Turn on the rule miner and Qodo learns your standards from review history" icon="lightbulb">
    Turn on the rule miner and Qodo discovers your team's standards automatically from your code review history, turning them into enforceable rules.

    See [Generate rules from pull request history with Rule Miner](/governance/rule-enforcement/rule-miner) for the full guide.
  </Accordion>

  <Accordion title="Customize every PR review with a REVIEW.md file in your repo root" icon="lightbulb">
    Add a `REVIEW.md` file at your repository root and Qodo applies the review instructions and guidelines it contains on every PR. It is a simple, repo-local way to customize your review.

    See [Apply REVIEW.md instructions to code review](/governance/use-review-md) for the full guide.
  </Accordion>

  <Accordion title="Route each severity your way: inline, summary, both, or drop" icon="lightbulb">
    Under **Advanced comment routing overrides** on the Display tab, decide where each severity lands: inline comments, the summary comment, both, or dropped entirely. High-severity findings always stay on at least one surface.

    See [Control review verbosity in pull requests](/code-review/review-verbosity) for the full guide.
  </Accordion>

  <Accordion title="Keep summaries lean: Findings visible per group tucks the rest behind a View link" icon="lightbulb">
    **Findings visible per group** collapses all but the top findings per severity behind a "View" link, so the summary stays scannable on busy PRs.

    See [Reduce review noise on pull requests](/code-review/reduce-review-noise) for the full guide.
  </Accordion>

  <Accordion title="Show, collapse, or hide each part of a finding: code, evidence, and all" icon="lightbulb">
    The description, code snippet, relevance, evidence, and agent prompt can each be set to hidden, collapsed, or expanded, so you can tune the comment from lean to verbose.

    See [Control findings visibility and expansion in pull requests](/code-review/findings-visibility) for the full guide.
  </Accordion>

  <Accordion title="Every finding has a copy-paste agent prompt: feed it to your IDE agent" icon="lightbulb">
    Every finding can include a copy-paste agent prompt. Hand it to your IDE agent to implement the fix with full context.

    See [Anatomy of a Qodo Code Review](/code-review/comment-anatomy) for the full guide.
  </Accordion>

  <Accordion title="Tweak Display settings with a live preview to see your comment before it ships" icon="lightbulb">
    Adjust your Display settings in the portal and a live preview shows exactly how your review comment will render as you change settings, so you can see the result before it ships.

    See [Configure Qodo using the portal](/configuration/portal-configuration) for the full guide.
  </Accordion>

  <Accordion title="Commit Qodo's fix in one click with committable suggestions (GitHub & GitLab)" icon="lightbulb">
    Enable committable code suggestions to apply Qodo's fix directly from the inline comment. Supported on GitHub and GitLab.

    See [Commit code fixes directly in the pull request](/code-review/commitable-code-suggestions) for the full guide.
  </Accordion>

  <Accordion title="Not a fan of tips? Turn them off under Display > Comment parts" icon="lightbulb">
    Prefer not to see the rotating tip on your PR comments? Turn off **Show tip of the day** in the portal under **Configurations > Display > Comment parts**. With the daily tip disabled, Qodo stops appending it to your PR summary comments.

    Open [Display](https://app.qodo.ai/configurations?tab=display) in the Qodo portal.
  </Accordion>

  <Accordion title="Switch off images and animations for a plain-text comment" icon="lightbulb">
    Turn off **Show images and animations** under **Configurations > Display > Notification comments** and Qodo renders text and markdown equivalents instead of the illustrations, dividers, section badges, and footer logo. Handy for air-gapped setups where the image host is unreachable, or if you simply prefer a plain comment.

    See [Configure Qodo using the portal](/configuration/portal-configuration) for the full guide.
  </Accordion>

  <Accordion title="Hide the parts of a finding you never read, like the evidence or the agent prompt" icon="lightbulb">
    Each block in a finding can be hidden outright rather than just collapsed, so the parts your team never opens stop taking up room in the comment. Set them under **Configurations > Display > Findings**.

    See [Control findings visibility and expansion in pull requests](/code-review/findings-visibility) for the full guide.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.