> Read the summary first. Challenge the claims. Decide where the risk is likely to be. Then use the code to verify those claims instead of using the code to discover them in the first place.

You get that with tiny commits, that make confirming the commits' text as easy as possible; if they're hierarchical it's even better, but that requires using a decent commits viewer (absolutely not github and the likes).

I think it's a fair point, now code gen is much quicker, keeping commits slim is a challenge in itself. Agree the big repo platforms don't really do any favours in that department