- Local Analysis: Catch bugs and security issues before you commit.
- Context-aware: Uses your repository’s custom rules, learnings, and settings.
- One-key Fixes: Generate prompts to fix issues instantly in your IDE.
- Flexible Modes: Review uncommitted changes, branches, or specific commits.
Getting started
Install and launch the cubic CLI:cubic to open the CLI and start a review.

Authentication
The first time you runcubic, it will automatically open your browser to sign in with your cubic.dev account. Once authenticated, you’re all set — no extra steps needed.
If you run into any authentication issues, press Ctrl+L to log out and re-authenticate.
Using with AI coding assistants
When using Claude Code, Codex, or other AI coding assistants, you can instruct them to use cubic for code review:Common Workflows
The CLI adapts to different stages of your development process.
1. Review Uncommitted Changes (Default)
Review code you are currently working on, before you commit.2. Review a Pull Request (Branch Review)
Compare your current branch against a base branch (e.g.,main) to catch issues before opening a PR.
3. Review a Specific Commit
Analyze changes introduced by a specific commit hash or reference.4. Custom Instructions
Focus the review on specific concerns like security or performance.Command Reference
The primary command iscubic review.
Options
| Option | Alias | Description |
|---|---|---|
--json | -j | Output results as JSON (for CI/automation) |
--base [branch] | -b | Review against a base branch (PR-style). Auto-detects base if no branch specified |
--commit <ref> | -c | Review a specific commit |
--prompt <instructions> | -p | Custom review instructions |
--base, --commit, and --prompt are mutually exclusive.