docs(cli): update generated docs

Author: fadeev

docs/docs/07-cli.md

@@ -241,6 +241,7 @@ ignite chain build [flags]
 **Options**
 
 ```
+      --check-dependencies        Verify that cached dependencies have not been modified since they were downloaded
       --clear-cache               Clear the build cache (advanced)
   -h, --help                      help for build
       --home string               Home directory used for blockchains
@@ -250,6 +251,7 @@ ignite chain build [flags]
       --release                   build for a release
       --release.prefix string     tarball prefix for each release target. Available only with --release flag
   -t, --release.targets strings   release targets. Available only with --release flag
+      --skip-proto                Skip file generation from proto
   -v, --verbose                   Verbose output
 ```
 
@@ -291,10 +293,12 @@ ignite chain init [flags]
 **Options**
 
 ```
-      --clear-cache   Clear the build cache (advanced)
-  -h, --help          help for init
-      --home string   Home directory used for blockchains
-  -p, --path string   path of the app (default ".")
+      --check-dependencies   Verify that cached dependencies have not been modified since they were downloaded
+      --clear-cache          Clear the build cache (advanced)
+  -h, --help                 help for init
+      --home string          Home directory used for blockchains
+  -p, --path string          path of the app (default ".")
+      --skip-proto           Skip file generation from proto
 ```
 
 **SEE ALSO**
@@ -317,15 +321,17 @@ ignite chain serve [flags]
 **Options**
 
 ```
-      --clear-cache         Clear the build cache (advanced)
-  -c, --config string       Ignite config file (default: ./config.yml)
-  -f, --force-reset         Force reset of the app state on start and every source change
-  -h, --help                help for serve
-      --home string         Home directory used for blockchains
-  -p, --path string         path of the app (default ".")
-      --proto-all-modules   Enables proto code generation for 3rd party modules used in your chain
-  -r, --reset-once          Reset of the app state on first start
-  -v, --verbose             Verbose output
+      --check-dependencies   Verify that cached dependencies have not been modified since they were downloaded
+      --clear-cache          Clear the build cache (advanced)
+  -c, --config string        Ignite config file (default: ./config.yml)
+  -f, --force-reset          Force reset of the app state on start and every source change
+  -h, --help                 help for serve
+      --home string          Home directory used for blockchains
+  -p, --path string          path of the app (default ".")
+      --proto-all-modules    Enables proto code generation for 3rd party modules used in your chain
+  -r, --reset-once           Reset of the app state on first start
+      --skip-proto           Skip file generation from proto
+  -v, --verbose              Verbose output
 ```
 
 **SEE ALSO**
@@ -992,81 +998,11 @@ Tools for advanced users
 **SEE ALSO**
 
 * [ignite](#ignite)	 - Ignite CLI offers everything you need to scaffold, test, build, and launch your blockchain
-* [ignite tools completions](#ignite-tools-completions)	 - Generate completions script
 * [ignite tools ibc-relayer](#ignite-tools-ibc-relayer)	 - Typescript implementation of an IBC relayer
 * [ignite tools ibc-setup](#ignite-tools-ibc-setup)	 - Collection of commands to quickly setup a relayer
 * [ignite tools protoc](#ignite-tools-protoc)	 - Execute the protoc command
 
 
-## ignite tools completions
-
-Generate completions script
-
-**Synopsis**
-
- The completions command outputs a completion script you can use in your shell. The output script requires 
-				that [bash-completion](https://github.com/scop/bash-completion)	is installed and enabled in your 
-				system. Since most Unix-like operating systems come with bash-completion by default, bash-completion 
-				is probably already installed and operational.
-
-Bash:
-
-  $ source <(ignite  tools completions bash)
-
-  To load completions for every new session, run:
-
-  ** Linux **
-  $ ignite  tools completions bash > /etc/bash_completion.d/ignite
-
-  ** macOS **
-  $ ignite  tools completions bash > /usr/local/etc/bash_completion.d/ignite
-
-Zsh:
-
-  If shell completions is not already enabled in your environment, you will need to enable it.  You can execute the following once:
-
-  $ echo "autoload -U compinit; compinit" >> ~/.zshrc
-
-  To load completions for each session, execute once:
-  
-  $ ignite  tools completions zsh > "${fpath[1]}/_ignite"
-
-  You will need to start a new shell for this setup to take effect.
-
-fish:
-
-  $ ignite  tools completions fish | source
-
-  To load completions for each session, execute once:
-  
-  $ ignite  tools completions fish > ~/.config/fish/completionss/ignite.fish
-
-PowerShell:
-
-  PS> ignite  tools completions powershell | Out-String | Invoke-Expression
-
-  To load completions for every new session, run:
-  
-  PS> ignite  tools completions powershell > ignite.ps1
-  
-  and source this file from your PowerShell profile.
-
-
-```
-ignite tools completions
-```
-
-**Options**
-
-```
-  -h, --help   help for completions
-```
-
-**SEE ALSO**
-
-* [ignite tools](#ignite-tools)	 - Tools for advanced users
-
-
 ## ignite tools ibc-relayer
 
 Typescript implementation of an IBC relayer