Post

Every commit starts with an intent. You implement it with an agent. Things change, and the new intent and learning lives in that conversation, which is gone by the time you commit. So ideally write the final change intent into the commit, before committing.

Working with an agent may make it easier to preserve context and implicit knowledge: it can reconstruct how the commit got to where it is now.

On the other hand, there are more things to check and manage. But the alternative is knowledge loss.

I am however convinced there is some balance possible in documenting just enough to prevent knowledge archaeology. "The cost of recording knowledge is small compared to the cost of acquiring knowledge." (Karl Wiegers)