Do the math yourself: A bug is picked up 2 week after commit. In the meantime, a good 4096+ commits have happened since. You are looking for the pathological case, at +- 12 commits.

Do you think each and every one of those are going to be "good" commits, commits that still "compile" or function. Possible, but unlikely given the insane velocity.

> commits that still "compile" or function

I see your point, but I don't think it's practically relevant.

Which model are you using? Before committing, I've never had a model, after claude 4.0, commit something before linting/parsing/compiling and running tests. In fact ,last project I fully vibe coded ended up with over 260 unit tests, without me even prompting for it!

If you're getting commits that don't compile at all, I would be interested in seeing your global memories. All the latest models seem to be test heavy.

Regardless, an agent from even a year ago would still be able to handle this case of teasing out functionality from git bisect, even if the overall code couldn't compile. First step would be to git log the relevant lines to filter out 99%.