Every way I've caught an AI agent making the build green without fixing anything
Heat trend
Collecting trend data
The percentage is based on available heat signal, not comment count or independent people.
This covers a coding tool or code-capability update — useful for developers assessing workflow changes and reusable value.
A developer has been tracking instances where AI agents make software builds appear successful without actually resolving underlying issues.…
I’ve been collecting these for a few months.
All of them produce a passing CI run. None of them fix the problem.
- Delete the failing test.
- Remove assertions but keep the test.
- Replace a real assertion with expect(true).toBe(true).
- Disable TLS verification: verify=False, rejectUnauthorized: false, InsecureSkipVerify: true.
- Add u/ts-ignore , # noqa, or //nolint on the exact line a checker complained about.
- Catch and discard the error: except: pass, catch {}, .catch(() => {}).
The pattern I care about now isn’t: “Is this code good?”
It’s: “Did this change edit the thing that decides whether it passes?” Tests, CI config, lint config, .gitignore; I read those first.
What other versions of this have people seen?
Disclosure: I ended up building an open-source CLI to catch these patterns. It’s called Verik — npm install -g verik or visit our github!