Update analyze command documentation

ABaldwinHunter · ABaldwinHunter · commit e9c247c7edc6 · 2016-08-24T15:23:11.000-04:00
Add information about -e and --dev flags
diff --git a/README.md b/README.md
@@ -75,7 +75,7 @@ A list of available commands is accessible by running `codeclimate` or
 $ codeclimate help
 
 Available commands:
-    analyze [-f format]
+    analyze [-f format] [-e engine(:channel)] <path> [--dev]
     console
     engines:disable engine_name
     engines:enable engine_name
@@ -90,7 +90,8 @@ Available commands:
 
 The following is a brief explanation of each available command.
 
-* `analyze`: Analyze all relevant files in the current working directory. All engines that are enabled in your `.codeclimate.yml` file will run, one after another. The `-f` (or `format`) argument allows you to set the output format of the analysis (using `json`, `text`, or `html`).
+* `analyze`: Analyze all relevant files in the current working directory. All engines that are enabled in your `.codeclimate.yml` file will run, one after another. The `-f` (or `format`) argument allows you to set the output format of the analysis (using `json`, `text`, or `html`). The `--dev` flag lets you run your own engines during
+development.
 * `console`: start an interactive session providing access to the classes within the CLI. Useful for engine developers and maintainers.
 * `engines:disable engine_name`: Changes the engine's `enabled:` node to be `false` in your `.codeclimate.yml` file. This engine will not be run the next time your project is analyzed.
 * `engines:enable engine_name`: Installs the specified engine (`engine_name`). Also changes the engine's `enabled:` node to be `true` in your `.codeclimate.yml` file. This engine will be run the next time your project is analyzed.
