Skip to main content
BetaGitHubGitLabBitbucket CloudAzure DevOps
Who can view and manage rules?
  • Admins can create, edit, enable, approve, and delete rules.
  • Members can generate rules in the portal. However, these rules appear in the Pending rules tab and require admin approval before becoming active. Members can also view active rules, pending rules, and review rule outcomes during code reviews.

​
View your rules

In the Qodo portal, navigate to Review Standards from the left menu.
Qodo portal Rules page showing the grouped rules table, summary analytics cards, grouping controls, and filter controls
The summary cards at the top show rule performance for the last 30 days. See Rule analytics for details.

​
Change how rules are grouped

Use the grouping controls above the table to change how rules are organized:
Rules table grouping controls showing Origin repo and List options

​
Anatomy of a rule

A rule consists of the following fields: Rule scope Scope defines where the rule is enforced. You can narrow the scope to limit enforcement:
  • Global (default): applies the rule to all repositories across all Git organizations.
  • Git organization: applies the rule to selected Git organizations.
  • Repository: applies only to selected repositories.
  • Path patterns: applies to specific directories or files within a repository. Path patterns are optional and can only be added after selecting a repository, and are especially useful for monorepos where different projects or services live under the same repository.
Rules extracted from supported files (such as AGENTS.md) are automatically scoped to the folder containing that file, with no additional portal configuration needed.
Scope can be edited for a single rule at a time from the rule’s side panel (see Edit rule), or for multiple rules at once (see Manage rules in bulk).

​
Generate a rule

Use this flow to describe a rule in natural language and let Qodo agent generate a structured draft.
1

Start rule generation

Generate rule button at the top of the Rules page
  1. From Rules, click Generate.
  2. Enter a short description of the rule’s intent.
  3. Click Generate rule.
Example prompts:
  • “Disallow console.log in production builds”
  • “Avoid SQL string concatenation with user input”
Generate rule dialog in Qodo portal with natural language description input field
2

Review the generated rule draft

Qodo generates a complete rule draft that can be edited before activation.
3

Related rules check

Before activation, Qodo checks for:
  • Conflicts
  • Duplicates
  • Overlapping scope
You can review related rules or revise the draft.
4

Click Accept & activate

Generated rule draft preview showing name, content, and examples ready for review
The rule is added to the table in the Rules tab and enforced automatically according to its defined scope (repositories and optional path patterns).
If you are a member (non-admin), your rule appears in the Pending rules tab for admin review before activation, unless an admin has enabled Auto-approve user suggestions. See Review and activate pending rules.

​
Manage existing rules

Management actions for existing rules are available from the actions menu (⋮) in the table in the Rules tab. These actions are optional and can be performed at any time by admins or team admins. To open the rule behind a specific finding, click the rule link in the finding’s Evidence section in the pull request. See Anatomy of a Qodo Code Review.

​
Manage rules in bulk

Multiple rules can be activated, deactivated, or rescoped at once from the Rules tab.
1

Select rules

Select the checkbox next to each rule, or select the checkbox in the table’s top row to select every rule at once.
Rules table with multiple rows selected, showing the bulk actions toolbar with Deactivate, Activate, and Define scope options
2

Choose an action

  • Activate or Deactivate: Update the enabled state for all selected rules.
  • Define scope: Set the scope for all selected rules at once. Select Global to apply the selected rules organization-wide, or Specific repositories to select a total of 25 entities (organizations and repositories), with an optional path pattern for each selected repository. See Rule scope for more details on scopes.
3

Confirm the action

A confirmation dialog appears before the action is applied. Confirm to apply the change to all selected rules.
Define scope for selected rules dialog, showing Global and Specific repositories options with Cancel and Apply buttons
Defining a scope in bulk replaces the current scope on every selected rule. This cannot be undone.

​
Automatic rule updates from files

Qodo continuously monitors files that have already been imported. When changes are merged to one of these files, Qodo processes them and automatically updates the Review Standards to reflect the file’s current contents. The scope of extracted rules is automatically determined by the file’s location in the repository. If a new supported file is added to a repository after that repository was imported, Qodo doesn’t detect it automatically. Re-import the repository from Import rules and skills to pick it up. New rules extracted from supported files are:
  • Added directly as active rules.
  • Enriched with category, severity, scope, and examples.
Only new rules are added this way. Changes to or deletions of existing rules in these files aren’t reflected. Manage those directly from the Rules tab.
Single-tenant customersIf you installed Qodo before the new setup wizard was introduced, your GitHub App may not have the Push event subscription enabled. Without it, Qodo cannot detect changes to supported rule files.To enable it:
  1. Go to your GitHub App settings page.
  2. Select Permissions & events.
  3. Scroll to Subscribe to events.
  4. Check Push.
  5. Click Save changes.
For more details, see GitHub’s documentation.

​
Fetch rules using get-qodo-rules skill

Supported AI coding agents can access your Review Standards directly using the get-qodo-rules skill. The skill fetches repository specific rules from the Qodo platform API, including organization, repository, and path-level rules, and loads them into the agent context. This allows the agent to reference the same rules that are defined in Qodo. This capability is optional and does not replace Qodo’s rule enforcement. It enables agents to use the rules already configured for the repository. Using the skill requires a Qodo API key and rules configured in the Qodo platform. For more information, see:

​
View import status from anywhere in the portal

Click Background activity in the top right corner of the portal to open the panel and check Rules and skills import progress without leaving your current page. Click the row to open the Rules tab.
Background activity panel showing the Rules and skills import row after a successful import
  • While an import is running, the Import button in the dialog is disabled and shows a loading icon.
  • The row only appears once import applies to at least one repository.

​
Next steps