@michaelqlarson The documentation should be as short as possible here. For example, listing the keys for the interactive prompt is not really helpful to the user when he/she types legit help.

More importantly, I think this command should be revised to be as automated as possible. The main benefit of this command would be that you don't need to manually verify that the test has passed or failed, but instead rely on the exit status of the test command to verify whether the commit is good or bad. That way, it will run all by itself. Ruby test suites will do this, for example (return 0 if all tests passed, or non-zero otherwise). (See the bottom of [this article](http://git-scm.com/book/en/Git-Tools-Debugging-with-Git) for more).