Fact-check your own claims about code you changed, BEFORE telling the user a change is done — to catch over-claims (wrong values, routes or functions you said you added/removed). HOW TO CALL: extract the concrete factual claims from what you're about to say and pass them in claims (one short sentence each) — you parse them far more reliably than truth can re-parse prose, and it's free since you're already writing the message. Also pass the raw message as a backstop. Each claim is checked against the indexed repo + working-tree git diff + logs and gets a cited supported / contradicted / refused verdict. Deterministic: the verdict comes from evidence, not from a model — so listing a claim can't make it pass. 'refused' means unverifiable, NOT confirmed.