Pipeline capabilities
Custom guardrails
Describe organization-specific pre-merge checks in natural language.
Test generation
Identify changed paths that need coverage and propose missing tests.
Docstring generation
Propose documentation for functions, classes, and modules.
Linters and scanners
Run focused static checks and security scanners, then surface the relevant results.
Context used by the pipeline
The pipeline can combine three context layers:- Codebase intelligence for architecture, dependencies, and established patterns.
- External context from linked issues, documentation, MCP servers, and web queries when configured.
- 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.Configure the pipeline
Choose checks, test a representative pull request, and tune the output before broader rollout.