> ## Documentation Index
> Fetch the complete documentation index at: https://autter.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Review rules

> Write clear, testable team standards in natural language and apply them across repositories.

Review rules tell the Autter platform which team-specific standards to check on every pull request.

Write rules in natural language. You do not need a repository YAML file or a regular expression to create a rule.

## Write an effective rule

A useful rule has three parts:

| Part                | Example                                                   |
| ------------------- | --------------------------------------------------------- |
| Scope               | Payment handlers                                          |
| Requirement         | Verify the authenticated account owns the payment method  |
| Reason or exception | Prevent cross-account charges; test fixtures are excluded |

Combined rule:

> Payment handlers must verify that the authenticated account owns the payment method before creating a charge. Test fixtures are excluded.

Keep each rule focused on one decision. Split a rule when it contains several unrelated requirements.

## Good rule patterns

Use rules for standards that can be checked from code and repository context:

* require tests for payment flows
* route environment access through the validated configuration module
* use design system tokens instead of raw color values
* prevent direct database access from HTTP controllers
* require authorization checks before account-scoped reads or writes
* reject deprecated APIs outside an approved legacy path

Avoid rules such as “write good code” or “follow best practices.” They do not give Autter or the author a testable condition.

## Roll out a rule safely

<Steps>
  <Step title="Start from an existing review comment">
    Choose a standard your team already applies repeatedly.
  </Step>

  <Step title="Write one testable requirement">
    Include the scope, expected behavior, and important exceptions.
  </Step>

  <Step title="Apply it to a small repository set">
    Start where maintainers can evaluate findings quickly.
  </Step>

  <Step title="Review false positives">
    Refine the wording or scope when valid code is flagged.
  </Step>

  <Step title="Expand the rule">
    Apply it more broadly only after the output is consistently useful.
  </Step>
</Steps>

<Info>
  Available enforcement controls can vary by plan and platform release. Check the rule editor in your Autter organization for the controls currently available to you.
</Info>