Back to AI/ML Overview
🚦 Knowledge Site · AI Coding Agents in the Delivery Pipeline · Approaches Weighed

Diff to DeployAgents made writing code cheap. They did not make verifying it cheap.

A team that adopts AI coding agents gets more changes, larger changes, and a new kind of change: edits to the agent itself. Review queues and CI capacity become the bottleneck, and the slow, shared end-to-end test environments fill up first. This site follows one change from diff to production, through code change, commit, pull request, review and CI/CD, and weighs the approaches at each stage with the drawback of each.

🎯The problem

Before agents, the slow step was writing the change, and review and CI were sized for that pace. With agents, a developer can open several pull requests in the time one took before. Nothing downstream got faster on its own. People skim reviews or the queue stalls, and the few end-to-end test environments fill up with runs that a lint would have stopped.

🔑The claim
Every stage of the pipeline has one job: move verification earlier, make it cheaper, and keep the part that must stay with a person small enough for a person to do well. Each page lists several approaches and what goes wrong with each. It is a design to adapt, not a standard.

🗺️What is inside

Three hook moments, three jobs

After each edit: fast deterministic checks. Before the agent stops: the affected tests. Before a push: the guard. What each hook can and cannot do, and why only the server is the gate.

The review receipt

Review on the developer machine before the pull request exists, then let CI verify that work by hash instead of repeating it. The laptop pre-pays; it is never trusted.

Lanes, and CI as a budget

Sort changes by what they can break, not by who wrote them. Merge queues, test selection and scheduling for scarce end-to-end environments. For a red build: triage, then a deterministic verify, then fix.

When the change is an agent

Reviewing a skill file like code, and building an that is fast, parallel and still honest: freeze the world instead of replaying the path, pick the smoke set from the diff, grade in three layers, and grow the test set from shadow runs.

🖱️How to read it

  • Each stage is one tab: what happens, a diagram, the approaches weighed, a recommended default, a configuration sketch, and side questions.
  • Every diagram is clickable. A box opens what it is and what it looks like in the running example.
  • A ? badge means a glossary term is attached; terms drill down into each other.
  • Product details were checked against current documentation. The patterns work with any coding agent.