Green CI from an agent is not a merge signal. It is a claim: "I ran something and it exited zero."...
Green CI from an agent is not a merge signal. It is a claim: "I ran something and it exited zero." Your job is to check whether that claim covers the bug, the intent, and the failure modes you care about.
I treat "tests pass" as the start of a short verification sequence — not the end of review.
1. Inspect the diff, not the summary
Open the file list first. Ignore the agent's narrative until you can answer:
Which files actually changed?
An AI agent can make CI go green without making the code right. Here's how that happens, and how far you can get catching it.
A familiar interaction with a coding agent looks like this: "I implemented the feature, updated the...
Your coding agent finishes a task and tells you the tests passed. You accept the report. Later, when...
When I look at a pull request, I do not really care that a job named test is green. I care that the...
This isn't a product pitch. I'm genuinely stuck on a trust problem and I want to know how others...
To audit AI-generated tests, score how many mirror the code instead of checking it. Green CI proves...
