predict answers a question before the expensive answer exists: if this branch merges, does the behavior change?

how it works

It runs your behavior target at both ends of a range, default main..HEAD. Matching results mean nothing will change, said in 1 line, costing 2 test runs. Different results and it prints the transition direction plus a full blame naming the most likely commit.

behavior change predicted: pass -> fail
most likely: 7f31ac rework feeder pipeline

the record

Every prediction is appended to the history log with a predicted: prefix on its state, so the record distinguishes forecasts from observations.

where it fits

Run it in CI on pull requests against the base branch. A predicted fail before merge is the cheapest moment to learn about a regression, and the blame output attached to it is the review comment.