That example is spot on and I won't pretend the tool solves it — it can see the field name changed, not that item_price can be zero.

Honestly it's made me think the more useful thing is a pre-commit prompt: "this change looks non-obvious, add a comment?" rather than a post-push summary. Different problem entirely.

Good 2 cents.

I literally had a similar case just now. In an integration, if a status field contained X it was changed to Y before the status processing code. My change acted on X hence failed due to status being changed to Y up front.

Once I find the offending line, I can easily see what happened, but the why is missing.

Fortunately in this case it was documented in the ticket, but would have been preferable to be in code. Without the ticket description I would have been lost.

So yeah for me and my team, a tool which tries to identify such cases and alert the dev "oy, this change might not be obvious to others and is lacking comments or commit message explanation" would be much more valuable I think.

Perhaps a more difficult task, though I've been surprised by how good these models are these days.