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

# Rule enforcement in code review

> An overview of how Qodo rules define and enforce your organization's engineering standards consistently across code reviews.

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</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><AzureIcon />Azure DevOps</Badge>
</div>

Rules are the explicit, enforceable conventions Qodo checks during code review. Each rule captures a single engineering standard: how code should be written, structured, or reviewed, so Qodo can apply it consistently across every pull request.

Rules can be added in three ways:

| Method                                                                                                  | How it works                                                                                                                                                          |
| ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **[Manual](/governance/rule-enforcement/generate-and-manage-rules)**                                    | Generate a rule from a natural language description in the portal.                                                                                                    |
| **[File-based](/governance/rule-enforcement/building-review-standards#supported-file-names-and-types)** | Import automatically from AGENTS.md, CLAUDE.md, and other supported files on push.                                                                                    |
| **[Rule Miner](/governance/rule-enforcement/rule-miner)**                                               | Discover patterns automatically from your organization's pull request history. Generated rules appear in Active Rules or Suggestions depending on your configuration. |

In cases where Review Standards are not applicable, Qodo applies its established best practice checks and configured compliance files. See [Rule enforcement without Review Standards](/governance/rule-enforcement/without-rule-system).

## Next steps

* [How Qodo builds your Review Standards](/governance/rule-enforcement/building-review-standards): See what Qodo builds automatically when Review Standards first connects to your repositories.
* [Generate and manage rules](/governance/rule-enforcement/generate-and-manage-rules): Create rules manually and manage existing ones.
* [Review and activate suggested rules](/governance/rule-enforcement/suggested-rules): Review and approve the rules Qodo surfaces before they are enforced.
* [Rule analytics](/governance/rule-enforcement/analytics): Track how rules perform across pull requests over time.