Skip to main content
GitHub
Enabled by default for new customers.
Existing multi-tenant customers can enable it directly from the Rules page in the Qodo portal. See Enable rules for existing customers.
This page explains how the Rule System is initialized for customers when Qodo is first connected to an organization’s repositories. During onboarding, Qodo helps teams establish a baseline rule set by importing existing standards, enriching them with additional context, and generating suggested rules based on real development activity.

​
What happens during onboarding

When you install Qodo in your Git organization, Qodo performs the following steps to initialize the Rule System.

​
Importing existing rules

Qodo discovers and imports existing rules from supported files in the organization’s repositories.
  • Rules can be extracted from full or partial documents
  • Relevant sections are identified, converted into rules, and optimized for code review
  • Imported rules are added to the Rules table
After import, rules are normalized and enriched to align with the Qodo rule system.
Qodo continues to monitor these files after onboarding. When changes are merged to your repository, new rules are automatically added and enriched. This also applies to any additional supported files added to repositories after onboarding.Single-tenant customers: If you installed Qodo before the new setup wizard, additional setup may be required.See Automatic rule updates from files for details.

​
Supported file names

  • AGENTS.md
  • CLAUDE.md
  • GEMINI.md
  • copilot-instructions.md
  • best_practices.md
  • RULE.md
  • .cursorrules
  • pr_compliance_checklist.yaml

​
Folder-level scoping in monorepos

Rules are automatically scoped to the folder containing the source file, at any depth. For example, rules extracted from src/payments/AGENTS.md are only applied to changes made to files under src/payments/ and any nested subfolders. A file placed at the root of a repository scopes its rules to that repository only, not across the entire organization. You can place supported files at different levels of your repository to control where rules apply, without any additional configuration in the portal. Different folders can have different rules, making it especially useful in monorepos where different services or packages follow their own conventions. The inferred scope is visible on the Rules page, where each rule displays the path it was scoped to.

​
Rule enrichment

Imported rules are enriched with additional structure to make them enforceable and reviewable. Enrichment includes category, severity, scope, and examples. This ensures imported rules behave the same as rules created directly in the portal.

​
Suggested rules generation

As part of onboarding, Qodo also generates a set of suggested rules based on the organization’s pull request history.
  • Based on retroactive analysis of recent PRs
  • Identifies repeated review patterns and behaviors
  • Suggested rules are not enforced automatically
All suggested rules require explicit admin review and approval before activation.

​
What to expect after onboarding

Within minutes of installing Qodo, you’ll start to see the following:
  • Imported rules appear in the Rules table
  • Suggested rules appear under Rules → Suggestions
  • No rules are enforced until explicitly activated
This approach enables teams to review, refine, and activate rules at their own pace while maintaining full control over enforcement.

​
Triggering additional suggested rules

After onboarding, you can optionally trigger additional suggested rule discovery as your review practices evolve. Add /scan_repo_discussions as a comment on any pull request to generate more suggested rules from recent discussions. Automatic, ongoing discovery will be available soon.