Oh dear. That reminds me of a story I saw here on HN at some point (might have been in the comments) about a dev team that didn't insist on any commit messages in their VCS, so everyone just put in a '.' to meet the requirement that a commit had to have a message for whatever source control system they were using.

My team doesn't have a strict commit message style guide, but good god it better be at least mildly descriptive of what's in the commit.

(I know you're joking, the thought of a 3 character alias to commit with a dummy message just sent shivers down my spine :)

Like this?

  $ cat << EOF > ~/.commit_reasons; strfile ~/.commit_reasons
  Testing...
  %
  Testify...
  %
  Testarossa...
  %
  Does it work yet?
  %
  How bout now?
  %
  Oops.
  %
  Fixed a thing.
  %
  EOF
  
  $ fortune ~/.commit_reasons | cowsay | git -F -