Practices
Gate every merge on automated checks
No change, from a person or an agent, merges until the full set of checks passes on that exact change.

A merge gate turns the principle of verifiable change into a mechanism. The repository refuses a merge until every required check reports success for the commit being merged.
How teams apply it
- Run the same checks locally and in the pipeline, from one task runner, so a green laptop means a green pipeline.
- Make the checks required in the repository settings, so nobody can bypass them by accident.
- Treat a flaky check as a broken check, and fix or remove it the same week.
What it looks like in practice
An agent opens a pull request with a change and the tests it wrote. The pipeline runs formatting, linting, unit tests and a security scan. When a check fails, the agent reads the output, fixes the change and pushes again. When everything passes, the owner reviews the diff and the evidence together and merges.
| Check | Catches | Typical time |
|---|---|---|
| Formatting and lint | Style drift, common bugs | Seconds |
| Unit tests | Broken behavior | One to two minutes |
| Security scan | Leaked secrets, known vulnerabilities | Under a minute |