Add some naming, structure, error conventions for Bash

### Usage
* All scripts should take a -h argument and return the usage. The usage should be in BNF or EBNF http://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form and should include every option the script can take and arguments as well. The script should also include usable examples below the EBNF. The script should use lower case for most arguments, unless the option 'negates' in which case it should be upper case. (this part may be getting a little too specific for a general purpose style guide, but I love -f and -f should be reserved for force, which will bypass error checking for admins who run with scissors.)