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

# How Qodo builds your Review Standards

export const AzureIcon = () => <svg className="azure-icon" viewBox="0 0 18 18" width="12" height="12" style={{
  display: "inline",
  verticalAlign: "middle",
  flexShrink: 0,
  background: "transparent"
}}>
    <defs>
      <linearGradient id="azure-gradient" x1="9" y1="16.97" x2="9" y2="1.03" gradientUnits="userSpaceOnUse">
        <stop offset="0" stopColor="currentColor" />
        <stop offset="0.16" stopColor="currentColor" />
        <stop offset="0.53" stopColor="currentColor" />
        <stop offset="0.82" stopColor="currentColor" />
        <stop offset="1" stopColor="currentColor" />
      </linearGradient>
    </defs>
    <path d="M17,4v9.74l-4,3.28-6.2-2.26V17L3.29,12.41l10.23.8V4.44Zm-3.41.49L7.85,1V3.29L2.58,4.84,1,6.87v4.61l2.26,1V6.57Z" fill="url(#azure-gradient)" />
  </svg>;

<div style={{ display: "flex", alignItems: "center", gap: "6px" }}>
  <Badge color="outline-purple" size="sm" shape="pill">Beta</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="github">GitHub</Badge>
  <Badge color="outline-provider" size="sm" shape="pill" icon="bitbucket">Bitbucket Cloud</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><AzureIcon />Azure DevOps</Badge>
</div>

<Note>
  Enabled by default for new customers. Existing customers may need to upgrade to the new installation wizard to enable it. See [Enable Review Standards for existing customers](/governance/rule-enforcement/enable-rules-existing-customers).
</Note>

This page explains how Qodo initializes the Review Standards when first connected to your organization’s repositories.

As it builds your Review Standards, Qodo helps teams establish a baseline rule set by importing existing standards, enriching them with additional context, and generating rules based on real development activity.

## How Qodo builds your Review Standards

When you install Qodo in your Git organization, Qodo performs the following steps to initialize the Review Standards.

### Importing existing rules

Qodo discovers and imports existing rules from supported files in the organization’s repositories.

* Rules can be extracted from full or partial documents.
* Relevant sections are identified, converted into rules, and optimized for code review.
* Imported rules are visible in the **Rules** tab on the Review Standards page.

After import, rules are normalized and enriched with category, severity, scope, and examples to align with the Qodo Review Standards, so they behave the same as rules created directly in the portal.

<Note>
  Qodo continues to monitor these files after the initial build:

  * When changes are merged, new rules are automatically added and enriched. This also applies to supported files added later. See [Automatic rule updates from files](/governance/rule-enforcement/generate-and-manage-rules#automatic-rule-updates-from-files) for details.
  * Only new rules are added. Changes to or deletions of existing rules in these files are not reflected. Manage those directly in [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules).
</Note>

<Warning>
  **Single-tenant customers:** If you installed Qodo before the new installation wizard, additional setup may be required.
</Warning>

### Supported file names and types

* `AGENTS.md`
* `CLAUDE.md`
* `GEMINI.md`
* `copilot-instructions.md`
* `best_practices.md`
* `RULE.md`
* All files in the Skills directories (e.g. `skills/<skill-name>/SKILL.md`)
* All files in the `.cursor/rules/` directory (including `.cursorrules` and `.mdc` files)
* `pr_compliance_checklist.yaml`

### Folder-level scoping in monorepos

Rules are automatically scoped to the folder containing the source file, at any depth. For example, rules extracted from `src/payments/AGENTS.md` are only applied to changes made to files under `src/payments/` and any nested subfolders.

A file placed at the root of a repository scopes its rules to that repository only, not across the entire organization.

You can place supported files at different levels of your repository to control where rules apply, without any additional configuration in the portal. Different folders can have different rules, making it especially useful in monorepos where different services or packages follow their own conventions.

The inferred scope is visible on the **Rules** page, where each rule displays the path it was scoped to.

## Rule discovery

As part of building your Review Standards, [Rule Miner](/governance/rule-enforcement/rule-miner) analyzes your organization’s pull request history to generate an initial set of rules.

* Based on retroactive analysis of recent PRs.
* Identifies repeated review patterns and behaviors.
* Rules are activated automatically.

## What to expect once your Review Standards are built

Within minutes of installing Qodo, you’ll start to see the following:

* Imported rules appear in the table in the **Rules** tab.
* Imported rules are active immediately and will be enforced on future pull request reviews.

Rule Miner starts analyzing your pull request history once the first pull request is opened on a repository after installation, not immediately at installation. Mined rules take longer to appear than imported rules. See [How Rule Miner generates rules over time](/governance/rule-enforcement/rule-miner#how-rule-miner-generates-rules-over-time) for timing details.

## Next steps

* [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules): Review what Qodo generated, create rules manually, and manage existing ones.
* [Rule Miner](/governance/rule-enforcement/rule-miner): Understand how Qodo continues to generate rules from your pull request history going forward.