Trunk-Based Development With Coding Agents: What Replaces Code Review?

说明与用途

Amp 用编码代理驱动的 trunk‑based 开发取代 PR，通过预推送检查、CI 门控、审计跟踪和代理线程链接满足 SOC 2 合规性。

问题

Engineering teams want to accelerate delivery by eliminating pull‑request bottlenecks while still meeting security and compliance requirements such as SOC 2.

结果

Amp’s trunk‑based, agent‑driven workflow eliminates pull requests while satisfying SOC 2 controls through restricted push access, signed commits, CI gates, and audit trails that link commits to agent threads.

工作流

• 1. Agent performs local pre‑push checks (formatter, type‑check, fast tests) and records results in the agent thread.
• 2. Agent reviews its own diff against origin/main, fixes findings, and limits to two review rounds.
• 3. If the change touches load‑bearing code, the owner is added to the thread for additional oversight.
• 4. Feature flags and revert rules are defined before commit.
• 5. Commit includes trailers (ticket, agent‑thread link, proof, review findings).
• 6. Push to main triggers CI that runs full validation pipeline (tests, infra checks, security scans).
• 7. CI blocks main if any check fails.
• 8. Commit is linked to the agent thread, providing an audit trail from discussion to deployment.

证据

SOC 2 doesn’t require pull requests. It requires that you think about your risks.

来源

The agent thread actually can replace the PR.

来源

Every change runs through the full validation pipeline: tests, infrastructure checks, security checks. Bad changes block main.

来源

Proof and review answer different questions. Proof shows the change works; a review asks whether it follows the team’s standards...

来源