docs(tutorials): add installation guide and feature overview for hooks

Author: crai0

docs/tutorials/auto_prepare_commit_message.md

@@ -4,42 +4,43 @@
 
 It can be desirable to use commitizen for all types of commits (i.e. regular, merge,
 squash) so that the complete git history adheres to the commit message convention
-without ever having to call `cz commit` manually.
+without ever having to call `cz commit`.
 
 To automatically prepare a commit message prior to committing, you can
-use a [Git hook](prepare-commit-msg-docs):
+use a [prepare-commit-msg Git hook](prepare-commit-msg-docs):
 
-> The [prepare-commit-msg] hook is invoked by git-commit right after preparing the
+> This hook is invoked by git-commit right after preparing the
 > default log message, and before the editor is started.
 
-This allows for enforcing the usage of commitizen so that whenever a commit is about to
-be created, commitizen is used for creating the commit message. Running `git commit` or
-`git commit -m "..."` for example, would trigger commitizen and use the generated commit
-message for the commit.
+To automatically perform arbitrary cleanup steps after a succesful commit you can use a
+[post-commit Git hook][post-commit-docs]:
 
-## How to
+> This hook is invoked by git-commit. It takes no parameters, and is invoked after a
+> commit is made.
 
-- Step 1: Create a new [`prepare-commit-msg`][prepare-commit-msg-docs] Git hook by running the following commands from the root of the Git repository:
+A combination of these two hooks allows for enforcing the usage of commitizen so that
+whenever a commit is about to be created, commitizen is used for creating the commit
+message. Running `git commit` or `git commit -m "..."` for example, would trigger
+commitizen and use the generated commit message for the commit.
 
-```sh
-cd .git/hooks
-touch prepare-commit-msg
-chmod +x prepare-commit-msg
-```
+## Installation
 
-- Step 2: Edit the newly created file and add the following content:
+Copy the hooks from [here](https://github.com/commitizen-tools/hooks) into the `.git/hooks` folder and make them
+  executable by running the following commands from the root of your Git repository:
 
-```sh
-#!/bin/sh
-COMMIT_MSG_FILE=$1
-exec < /dev/tty && cz commit --dry-run --write-message-to-file $COMMIT_MSG_FILE || true
+```bash
+wget -o .git/hooks/prepare-commit-msg https://github.com/commitizen-tools/hooks/prepare-commit-msg.py
+chmod +x .git/hooks/prepare-commit-msg
+wget -o .git/hooks/post-commit https://github.com/commitizen-tools/hooks/post-commit.py
+chmod +x .git/hooks/post-commit
 ```
 
-See the Git hooks documentation on [`prepare-commit-msg` hooks][prepare-commit-msg-docs] for details on how this works.
-
-[prepare-commit-msg-docs]: https://git-scm.com/docs/githooks#_prepare_commit_msg
+## Features
 
-## Drawbacks
+- Commits can be created using both `cz commit` and the regular `git commit`
+- The hooks automatically create a backup of the commit message that can be reused if
+  the commit failed
+- The commit message backup can also be used via `cz commit --retry`
 
-If additional hooks are used (e.g. pre-commit) that prevent a commit from being created,
-the message has to be created from scratch when commiting again.
+[post-commit-docs]: https://git-scm.com/docs/githooks#_post_commit
+[prepare-commit-msg-docs]: https://git-scm.com/docs/githooks#_prepare_commit_msg