Skip to main content
The pipeline is Autter’s automated layer that runs before any code reaches your main branch. It handles pre-merge quality checks, test coverage enforcement, docstring generation, and security scanning — all configurable through a single file. Create .autter/pipeline.yml in your repository to activate pipeline automation and choose which template and checks apply to your project.
Changes to .autter/pipeline.yml take effect on the next pull request opened after the file is committed. Existing open PRs are not re-evaluated.

​
Configuration file

.autter/pipeline.yml
template: security-audit
config:
  severity_threshold: medium
  block_on_findings: true
  notify:
    - slack: "#security-alerts"
    - email: security@yourcompany.com

​
Configuration fields

​
template
string
The pipeline template to use. Templates are pre-built CI/CD configurations for common workflows. See Available templates below for the full list.
​
config.severity_threshold
string
The minimum severity level that Autter flags as a finding. Accepts "low", "medium", or "high". Findings below this threshold are silently ignored.Set to "high" to only surface critical issues. Set to "low" to surface everything.
​
config.block_on_findings
boolean
Whether Autter blocks the merge when findings at or above the severity_threshold are detected. Set to true to enforce a hard gate; set to false to report findings without blocking.
​
config.notify
array
Notification channels to alert when findings are detected. Accepts a list of Slack channel references (prefixed with #) or email addresses.
notify:
  - slack: "#security-alerts"
  - email: security@yourcompany.com

​
Available templates

Templates are pre-built pipeline configurations for common workflows. Choose the one that matches your team’s primary concern, then tune the config block to adjust thresholds and notifications.
Pipeline Templates are currently in beta and available to Pro and Enterprise users only.
TemplateDescription
standard-reviewBasic code review with linting and type checking
security-auditFull vulnerability scanning with SAST/DAST analysis
performance-gateAutomated performance regression detection
compliance-checkSOC2 and GDPR compliance verification

​
Pipeline commands

In addition to templates, Autter exposes three first-class pipeline commands you can reference in natural language guardrails and pipeline steps:
Custom pre-merge checksDefine your own code quality checks in plain English — no YAML configurations or complex regex patterns needed. Autter interprets the natural language description and applies it to every PR.
.autter/pipeline.yml
template: standard-review
config:
  severity_threshold: medium
  block_on_findings: true
Use _guardrail to encode team-specific rules that don’t fit into a standard template, such as “all API endpoints must include rate limiting” or “no direct database access from controller files.”

​
Steps to get started

1

Create the .autter directory

At the root of your repository, create the .autter/ directory:
mkdir .autter
2

Add pipeline.yml

Create .autter/pipeline.yml and choose a template that matches your workflow:
.autter/pipeline.yml
template: standard-review
config:
  severity_threshold: medium
  block_on_findings: false
  notify:
    - slack: "#eng-reviews"
3

Commit and open a pull request

Commit the file to your default branch. The configuration takes effect on the next pull request opened after the commit is merged.