I agree with this wholeheartedly. If writing a detailed, multiparagraph commit message, assume the target audience is future you. Most likely, a time-pressed d

I agree with this wholeheartedly. If writing a detailed, multiparagraph commit message, assume the target audience is future you. Most likely, a time-pressed dev on the far side of the world will think your commit broke something and send a 2:00 AM message of "URGENT: code broke CRITICAL customer request" with a link to the commit, whatever JIRA issue they are working on, and zero additional context. They will NOT bother to read the message (likely explaining how they got into their pickle in the first place) but will see your email, send a message, and do whatever it is they do while waiting for someone else to figure out the problem. You, being that someone else, will now have an excellent starting point on the top priority for the day. Much better than if your message had just been "fixed it".