I can understand that, but since I put almost everything under git, it's less interesting to me.

However, personally, as part of my standard setup, I unalias all the common commands, in case some (IMHO misguided) sysadmin decides to inflict behaviour-changing options on standard commands via aliases. I'm all for a customized environment, but the standard commands (like ls, rm, cp, mv, ...) have to *work* the same or stuff breaks. Instead, I make my own shell functions, like e which is a wrapper around whatever my favourite editor is with name-remembering. I don't make an alias or function which has the same name as one of the usual commands as I've wasted too much time trying to figure out why a pipeline wasn't working due to ls not really being ls.