vero

AI-powered code review in your terminal — powered by Claude AI. Review your staged changes, branch diffs, or individual files before you push.

Install

npm install -g vero

Quick start

1. Get your API key

Open your Vero dashboard → Organisation Settings → Local API Key → Copy

2. Configure

vero config --url https://your-vero-server.com --key vero_xxxxxxxxxxxxxxxx

3. Review

git add .
vero review

Commands

vero config

vero config --url https://your-vero-server.com --key vero_xxx
vero config --show          # print current config

vero review

| Flag | Description | |------|-------------| | (default) | Review staged changes | | --diff <branch> | Review changes vs a branch (e.g. main) | | --file <path> | Review a single file | | --tech <stack> | Tech stack hint — e.g. "React 18, TypeScript" | | --no-arch | Skip architecture analysis (faster) | | --min-severity <s> | Show only critical, warning, or info | | --json | Output raw JSON (for CI pipelines) |

Examples

# Review staged files
git add src/
vero review

# Review everything changed vs main
vero review --diff main

# Review one file
vero review --file src/Services/AuthService.cs

# CI-friendly: block on critical issues, suppress info noise
vero review --diff main --min-severity warning

# Get machine-readable JSON
vero review --json > review.json

Exit codes

| Code | Meaning | |------|---------| | 0 | No critical findings — safe to push | | 1 | Critical findings found |

Use exit codes in CI or git hooks to block bad code automatically.

Pre-push git hook

Create .git/hooks/pre-push (and chmod +x on Mac/Linux):

#!/bin/sh
echo "Running Vero code review..."
vero review --diff origin/main --min-severity critical

Now every git push automatically reviews your changes first.

Requirements

• Node.js 18 or higher
• Git installed and in PATH
• A Vero server URL and API key

License

MIT