> ## 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.

# Pipeline automation

> Run custom guardrails, test generation, docstring generation, linters, and scanners before merge.

Autter pipeline automation adds focused checks and finishing steps to the pull request workflow. It runs before merge and works alongside your existing CI/CD pipeline.

<Frame caption="Placeholder: replace with an approved pipeline configuration screenshot.">
  <img src="https://mintcdn.com/autter/ZqVSJE8MeDV-Tn7Q/images/placeholders/pipeline-builder.svg?fit=max&auto=format&n=ZqVSJE8MeDV-Tn7Q&q=85&s=c8b98f117fc50a076a65c5bf237f5c24" alt="Placeholder showing modular Autter checks for guardrails, tests, docstrings, linters, and scanners" width="1200" height="620" data-path="images/placeholders/pipeline-builder.svg" />
</Frame>

## Pipeline capabilities

<CardGroup cols={2}>
  <Card title="Custom guardrails" icon="shield-check" href="/configuration/rules">
    Describe organization-specific pre-merge checks in natural language.
  </Card>

  <Card title="Test generation" icon="flask-vial" href="/configuration/pipeline">
    Identify changed paths that need coverage and propose missing tests.
  </Card>

  <Card title="Docstring generation" icon="file-lines" href="/configuration/pipeline">
    Propose documentation for functions, classes, and modules.
  </Card>

  <Card title="Linters and scanners" icon="magnifying-glass" href="/configuration/pipeline">
    Run focused static checks and security scanners, then surface the relevant results.
  </Card>
</CardGroup>

## Context used by the pipeline

The pipeline can combine three context layers:

1. **Codebase intelligence** for architecture, dependencies, and established patterns.
2. **External context** from linked issues, documentation, MCP servers, and web queries when configured.
3. **Linters and scanners** for deterministic findings that support the review.

## Fit Autter into CI/CD

Use Autter as a pre-merge review layer. Keep build, test, deployment, and environment-specific verification in your existing CI/CD system.

A practical division of responsibility is:

| Workflow                              | Primary owner                    |
| ------------------------------------- | -------------------------------- |
| Build and compile                     | Existing CI                      |
| Full test suite                       | Existing CI                      |
| Deployment checks                     | Existing CI/CD                   |
| Codebase-aware review                 | Autter                           |
| Team guardrails                       | Autter                           |
| Focused generated tests or docstrings | Autter, followed by human review |

## Review generated changes

Generated tests can encode the wrong behavior. Generated docstrings can make incorrect assumptions sound authoritative. Review both before accepting them.

<Warning>
  Do not use generated tests as proof that a requirement is correct. Validate the expected behavior independently.
</Warning>

<Card title="Configure the pipeline" icon="sliders" href="/configuration/pipeline">
  Choose checks, test a representative pull request, and tune the output before broader rollout.
</Card>