Configure the Autter pipeline from the hosted platform. The pipeline can combine codebase-aware checks with linters, scanners, and generation steps.
Available workflow types
Custom checks
Test generation
Docstring generation
Linters and scanners
Use a custom guardrail to describe a pre-merge quality check in natural language.Example:
All public API routes must apply rate limiting before calling application services.
Use test generation to identify changed code paths that need coverage and propose missing tests.
Use docstring generation to propose documentation for functions, classes, and modules.
Select focused static checks and security scanners that match the repository’s stack. Autter publicly describes a catalog of more than 40 linters and scanners.
Choose the repository
Open the repository’s settings in the Autter platform.
Select focused checks
Enable checks that match the languages, frameworks, and risks in that repository.
Add custom guardrails
Describe organization-specific requirements in clear, testable language.
Run a representative pull request
Verify that findings are relevant and generation steps produce code your team would accept.
Adjust before enforcing
Remove noisy checks and refine broad guardrails before relying on them as merge gates.
Generated tests and docstrings are proposed changes. Review them with the same care as code written by a developer or coding agent.
