Available commands

This page provides a complete reference for all commands and options available in AI Code Reviews in CLI. Use it to understand what each command does, when to use it, and how to combine options for common workflows.

Command structure

bitoreview <command> [options]

For convenience, you can also use the short alias br instead of bitoreview:

br <command> [options]

Commands overview

Command
Description

review

Analyze code changes and generate AI-powered feedback

config

Manage configuration settings and API keys

--help

Display help information

--version

Display the installed CLI version

review command

The review command is the core of the CLI. It analyzes your code changes and highlights issues related to bugs, security, performance, and overall code quality.

Basic syntax

bitoreview review [files...] [options]

Examples

Review scope options

--type, -t <type>

Specify which changes to review.

Supported values:

  • all (default) - Review both committed and uncommitted changes

  • uncommitted - Review only working directory changes

  • committed - Review only committed changes that have not yet been pushed

Examples:

--base <branch>

Compare changes against a specific branch.

Example:

--base-commit <commit>

Compare changes against a specific commit hash.

Example:

Review quality options

--mode <mode>

Control the depth and breadth of the review.

Supported values:

  • essential - Shows only HIGH severity issues for rapid feedback

  • comprehensive (default) - Shows all severity levels for thorough analysis

Examples:

--focus <area>

Concentrate the review on specific code quality aspects.

Supported values:

  • security - SQL injection, XSS, authentication, data validation

  • performance - Memory leaks, inefficient algorithms, bottlenecks

  • bugs - Logic errors, edge cases, runtime issues

  • best-practices - Code style, design patterns, maintainability

  • tests - Test coverage, test quality, testability

  • documentation - Comments, documentation quality, code clarity

Examples:

--severity <level>

Filter issues by minimum severity level.

Supported values:

  • high - Critical issues that must be fixed

  • medium - Important issues that should be addressed

  • low - Minor suggestions and style improvements

Examples:

Output options

--interactive, -i

Enable interactive mode to review and apply fixes one by one.

Example:

--plain

Output plain text without colors or formatting, suitable for logs and CI/CD.

Example:

--prompt-only

Minimal output optimized for AI agent integration.

Example:

--no-color

Disable colored output (similar to --plain but retains structure).

Example:

SCM options

--scm <type>

Override automatic SCM detection.

Supported values:

  • git - Git repository

  • svn - Subversion repository

  • hg - Mercurial repository

  • p4 - Perforce repository

  • plain - No version control (analyze files directly)

Example:

Configuration options

--config, -c <path>

Use a custom configuration file path instead of .bitoreview.yaml in the project root.

Example:

--api-key <key>

Provide API key directly via command line (overrides environment and config file).

Example:

--cwd <path>

Set the working directory for the review.

Example:

Debugging options

--debug, -d

Enable debug output for troubleshooting.

Example:

--verbose, -v

Enable verbose logging for detailed information.

Example:

--max-retries <number>

Set the number of retry attempts for API calls (default: 2).

Example:

config command

Manage configuration and API keys.

Set API key

Interactive mode (prompts for key):

Direct mode (provide key in command):

Show API key

Display your configured API key (masked for security).

Global options

--help, -h

Display help for any command.

Examples:

--version

Show the installed CLI version.

Example:

Option combinations

AI Code Reviews in CLI allows you to combine multiple options for precise control:

Last updated