I am lazy, and want to use git bisect to find a commit which introduced a failure with little work as possible.

I don't see a reason to supply a good-hash myself.

I think these input should be enough:

* a script which return 0 on success, and other on failure
* git is on a branch (not detached head). And test fails

The tool bisect (or a wrapper) could jump back in git history to find a good-hash itself.

Question: How to get this done?