Skip to main content

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.

Autter works out of the box with no configuration required. Connect your repository and your first pull request is analysed automatically using sensible defaults that cover the most common issues. When you’re ready to tailor Autter to your team’s specific standards, two configuration files give you full control:
FilePurposeLocation
autter.config.ymlRule categories and severity levelsRepository root
.autter/pipeline.ymlPipeline automation and pre-merge checks.autter/ directory at repo root
Both files are optional. If neither is present, Autter uses its default ruleset, which covers security vulnerabilities, performance anti-patterns, and common convention violations.

​
autter.config.yml

Place this file at the root of your repository to control which rule categories Autter enforces and how strictly it enforces them.
autter.config.yml
rules:
  security:
    severity: block          # prevent merge
  performance:
    severity: warn           # comment but allow merge
  conventions:
    severity: info           # informational only
  deprecated_apis:
    severity: block
    exceptions:
      - path: "legacy/**"    # known legacy code, don't block

​
Severity levels

Each rule category accepts one of three severity levels:
LevelEffect
blockPrevents merge until the issue is resolved
warnAdds a review comment but allows merge to proceed
infoInformational only — no action or approval required
Use block for issues that are never acceptable in your codebase (security vulnerabilities, breaking API changes). Use warn for patterns your team cares about but handles case-by-case. Use info for nudges and style preferences.

​
.autter/pipeline.yml

Place this file in a .autter/ directory at your repository root to configure automated pre-merge checks, pipeline templates, and notification routing.
.autter/pipeline.yml
template: security-audit
config:
  severity_threshold: medium
  block_on_findings: true
  notify:
    - slack: "#security-alerts"
    - email: security@yourcompany.com
See Pipeline for the full reference.

​
Next steps

Rules

Define custom review rules and configure severity levels for each category.

Pipeline

Configure pre-merge checks, pipeline templates, and notification channels.