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

# Review Standards in code review

> Review Standards are how Qodo defines and enforces 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 Cloud</Badge>
  <Badge color="outline-provider" size="sm" shape="pill"><AzureIcon />Azure DevOps</Badge>
</div>

Review Standards are how Qodo turns your organization's engineering conventions into something that can actually be enforced: consistently, at scale, and in context.

Modern teams rely on a mix of linters, reviewer habits, and tribal knowledge to maintain code quality. Over time, those standards drift. Some live in documentation no one reads, others exist only in the heads of senior engineers.

As AI accelerates code creation, these gaps become more visible. Review Standards address this with a central, living system for defining and enforcing how code should be written and reviewed.

## Breakdown of Review Standards

Review Standards bring together the ways Qodo captures and enforces how your team writes and reviews code:

* **Rules:** explicit, enforceable conventions Qodo checks on every pull request. See [Rule enforcement](/governance/rule-enforcement).
* **Skills:** reusable review capabilities you can manage and enforce across repositories. See [Manage skills across repositories](/governance/manage-skills-across-repositories).

## Explore Review Standards

<CardGroup>
  <Card title="Building your Review Standards" icon="rocket" href="/governance/rule-enforcement/building-review-standards" horizontal>
    See what Qodo builds automatically when Review Standards first connects to your repositories.
  </Card>

  <Card title="Rule enforcement" icon="gavel" href="/governance/rule-enforcement" horizontal>
    Define and enforce explicit rules on every pull request.
  </Card>

  <Card title="Suggested rules" icon="lightbulb" href="/governance/rule-enforcement/suggested-rules" horizontal>
    Review and activate rules Qodo surfaces from your code and review history.
  </Card>

  <Card title="Manage skills" icon="puzzle-piece" href="/governance/manage-skills-across-repositories" horizontal>
    Monitor and enforce skills across your repositories.
  </Card>
</CardGroup>

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