anchor.diff:        `globus transfer async-transfer --help` for an example
     - Comment liberally in source
     - Every command gets its own module, named after the command name
  -  - Use absolute imports everywhere
  -  - Avoid circular imports whenever possible -- given the choice between adding
  -      a new module or adding a circular import, add the new module
  -  - Import non-`globus_cli` modules and packages before importing from within
  -      `globus_cli`
     - Think very hard before adding a new dependency -- keep the dependencies of
         `globus_cli` as lightweight as possible
  -  - Use named parameters, not positional arguments
     - Use the verbs `create`, `show`, `update`, and `remove` for underlying API
         CRUD operations
   
  
positive.code: 
  First off, thank you so much for taking the time to contribute! :+1:
  
  This document is a set of guidelines for making modifications to the CLI, not a
  set of strict rules.
  Sometimes it's okay to go off-book if you have a good reason, so use your best
  judgement.
  Feel free to propose changes to this document in a pull request.
  
  QuickStart
  ----------
  
  Impatient? Want to get hacking on this right away? Have ideas and can't wait to
  share them with us?
  A few quick rules if you don't want to read this full document:
  
    - All of your code *must* pass `flake8`. We won't consider merging code which
        doesn't pass `flake8`
    - Check if there's a matching
        https://github.com/globus/globus-sdk-python/issues[issue]
        before opening a new issue or pull request
  
  Developer Setup
  ---------------
  
negative.code: 
  Do it:
  
    - `make release` to build dists, upload via twine, and tag the release
    - push the newly created version tag to GitHub
    - Ensure that `docs.globus.org` gets updated with new docs/changelog
        Procedure is set in that repo.
  