title: Standard to follow when writing git commit messages
body: <p>I find myself managing very many files (over 60 but below 70) and my commit messages so far follow this pattern:
  when I have added something like on <code>layout.css</code>, my commit message is <em>"added something on layout.css file"</em>, and when I remove something, my commit message is <em>"removed something from layout.css file"</em>.</p>
  
  <p>Some files down the line, I look at my commits feed and <em>added...</em> and  <em>removed...</em> messages dominate. Sometimes I don't remember what I removed or what I added in <code>layout.css</code> since I make so many changes at a go and so I struggle to come up with an appropriate commit message.</p>
  
  <p>Is there a standard I should follow to help me come up with my commit messages?</p>