Skip to main content
Autter sits at the merge layer of your CI/CD pipeline and runs automated checks before any code reaches your main branch. Catch issues, generate missing tests, and document your code — all without changing your existing workflow.

​
Pipeline commands

Three built-in commands give you control over what runs on every PR:

_guardrail

Custom checks — create your own pre-merge code quality checks in natural language. No YAML configs or complex regex patterns needed.

_test

Unit test generation — check test coverage and immediately generate any missing tests for changed code paths.

_generate

Docstring generation — create docstrings to make functions, classes, and modules easier to understand in the future.

​
Pipeline configuration

Autter pipelines are configured in a single YAML file at .autter/pipeline.yml. Use built-in templates as a starting point, then customize enforcement levels to match your team’s standards. 
# .autter/pipeline.yml
template: security-audit
config:
  severity_threshold: medium
  block_on_findings: true
  notify:
    - slack: "#security-alerts"
    - email: security@yourcompany.com
You can also configure per-rule severity levels directly: 
# autter.config.yml — customise enforcement levels
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

​
Available pipeline templates

Autter ships with four templates that cover the most common pre-merge workflows:
The default template. Runs code quality checks, convention detection, and test coverage analysis on every PR. Best for teams getting started with automated review.Checks included:
  • Bug and logical error detection
  • Convention drift from your merge history
  • Test coverage for changed files
  • PR summary generation
Templates are starting points, not constraints. You can extend any template with custom _guardrail checks written in natural language.

​
Built for your CI/CD pipeline

Custom guardrails

Define your own pre-merge quality checks in natural language. No YAML configs or complex regex patterns needed.

Test generation

Automatically detect coverage gaps and generate missing unit tests for changed code paths.

Docstring generation

Auto-generate clear, consistent documentation for functions, classes, and modules.

40+ linters and scanners

Security scanners and linters catch bugs early — and Autter filters out the noise from false positives.

Branch policies

Enforce branch protection rules and ensure PRs meet your quality bar before merging.

Modular pipeline

Pick and choose which checks to run. Enable or disable any step with a single toggle.