— Sri Rang, Solutions Architect @ Qodo
Per-repo, version-controlled
alongside the code
Org-wide governance
overrides repo rules
- title: "Work item must be linked in the PR description"
objective: "Ensure every PR is traceable to a work item"
success_criteria: "PR description contains AB#1234"
failure_criteria: "No AB# reference found in the PR description"
compliance_label: true
category: "traceability"
external_id: "ORG-POLICY-001"
- title: "No secrets or connection strings in committed code"
compliance_label: true
category: "security"
severity: "critical"
external_id: "ORG-POLICY-002"
.pr_agent.toml:
[config]
add_repo_metadata = true
add_repo_metadata_file_list = [".qodo/rules.yaml"]
On the next PR, Qodo:
.qodo/rules.yaml — no LLM step| Constraint | Detail |
|---|---|
File must end in .yaml or .yml |
.json, .toml, .md not picked up |
| YAML list at the top level | Dict at root → skipped with warning |
title is the only required field |
All other fields default |
compliance_label: true adds a blocking label |
Defaults to false |
enable_rules_platform: true overrides file rules |
Platform rules replace repo rules entirely |