I'm not a coder. I build things with an AI coding assistant (Claude), and a while ago I noticed something that bugged me: it would say "fixed!" and the fix would look fine, but nothing actually checked that it stayed fixed.
So I made a small tool called Bite . It asks one question about every recent fix:
If this change disappeared, would any test notice?
It takes the change back out of a copy of the project and runs the tests. If they fail, great: a test is guarding that fix. If they still pass, nothing would warn you if the fix broke later.
This week I did the obvious thing and pointed Bite at its own code. It didn't go the way I expected.
Bite flagged itself, and Bite was wrong
The first run flagged one of Bite's own early commits: "no test noticed it was gone."
That sounded bad, so we dug in. It turned out the flag was wrong, and the reason was sneaky. That commit created Bite's main files. To "take the change out", Bite deleted them from its copy.…