Skip to main content
Qodo enforces code quality and organizational standards even when Review Standards are not available or not enabled. In these cases, Qodo uses a repository-based enforcement approach, where standards are defined directly in configuration files within your codebase. Before the introduction of the Rule System in version 2.1, this was the primary way teams defined and enforced code review standards. It continues to be used in environments where Review Standards are not applied or where standards are managed at the repository level.

​
How enforcement works

In this approach, Qodo relies on rule definitions provided through repository files. Supported file names include:
  • AGENTS.md
  • CLAUDE.md
  • GEMINI.md
  • copilot-instructions.md
  • RULE.md
  • .cursorrules
  • best_practices.md
  • pr_compliance_checklist.yaml
These files define coding standards, patterns, and requirements such as security checks, ticket validation, and process rules. Qodo uses these files as the source of truth for how code should be reviewed.

​
During code review

When analyzing a pull request, Qodo:
  • Scans code changes to identify potential issues such as bugs, logic errors, and anti-patterns
  • Applies Best Practices to check how code is written (patterns, structure, conventions)
  • Runs Custom Compliance checks to validate required conditions and policies
Suggestions and findings are surfaced directly in the pull request based on these inputs, enabling consistent and customizable code review without requiring centralized rule management.

​
Next steps

  • Best Practices: Define coding standards and influence code suggestions.
  • Custom Compliance: Enforce requirements like security checks and validation rules.
  • Review Standards: Manage and enforce rules centrally across your organization.