It's not the exact key strikes I'm trying to record, it's more seeing how the shape of the code changes over time (e.g. variable names changing as the problem i

It's not the exact key strikes I'm trying to record, it's more seeing how the shape of the code changes over time (e.g. variable names changing as the problem is understood more fully). My code commits tend to be when I've reached a milestone (made a test pass for example), but I don't commit enough to understand the thought process that made me write the code that way.