> ## 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 Code Governance

> Qodo governance enforces coding standards, security policies, and compliance rules automatically across your organization.

Qodo governance is built for engineering leaders who need consistent standards enforced across every repository, automatically, at scale, and without manual intervention, improving codebase health across your entire organization.

## Centralized governance

Manage and monitor code review activity across all your repositories from a single location.

<CardGroup cols={3}>
  <Card title="Manage code review across repositories" icon="server" href="/governance/repositories">
    Learn how repositories, services and teams are connected to understand how code changes impact the full system.
  </Card>

  <Card title="Monitor organization-wide findings" icon="chart-bar" href="/governance/view-all-findings-in-organization">
    See a complete history of findings, decisions, and codebase health.
  </Card>

  <Card title="Manage skills across repositories" icon="puzzle-piece" href="/governance/manage-skills-across-repositories">
    Monitor, manage, and enforce skills across repositories to ensure consistent application of your organization's coding standards.
  </Card>
</CardGroup>

## Review Standards

Define and enforce your organization's engineering standards consistently across every pull request.

<CardGroup cols={2}>
  <Card title="Review Standards in code review" icon="star" href="/governance/review-standards">
    Review Standards are how Qodo turns your organization's engineering conventions into something that can actually be enforced: consistently, at scale, and in context.
  </Card>

  <Card title="Rule enforcement" icon="gavel" href="/governance/rule-enforcement">
    Explicit, enforceable conventions Qodo checks during code review, capturing how code should be written, structured, or reviewed across every pull request.
  </Card>
</CardGroup>
