Git bisect, without remembering the commands.
Bisect is a binary search for the commit that introduced a regression. It works well and almost nobody uses it, because the sequence of commands is easy to get wrong and easy to abandon halfway.
What the panel does
You give it a known-bad commit, which defaults to HEAD, and a known-good one. FluxGit checks out the midpoint and asks one question: is this commit good or bad? You build, you test, you mark it. It tells you roughly how many steps remain and how many revisions are still in play, so you know whether you are two answers from the truth or ten.
When it lands, it names the first bad commit and offers to reveal it in the graph, in context, with the rest of the history around it.
Stopping is a first-class action
The reason people avoid bisect is the fear of being stranded on a detached HEAD in the middle of a session. Stopping ends the session and returns you to the commit you started from. It is a button, not a command you have to look up.