Reviewing Uncommitted Changes
Use --dirty to review working tree changes before committing:
roborev review --dirty # Queue review of uncommitted changesroborev review --dirty --wait # Wait for review and show resultWhat Gets Reviewed
The --dirty flag includes:
- Staged changes
- Unstaged changes to tracked files
- Untracked files
Options
| Flag | Description |
|---|---|
--wait | Wait for review to complete |
--quiet | Suppress output |
--agent <name> | Use specific agent |
--reasoning <level> | Set reasoning depth |
Exit Codes
The --wait flag exits with:
- Code 0 for passing reviews
- Code 1 for failing reviews
This is useful for CI or pre-commit workflows:
if ! roborev review --dirty --wait --quiet; then echo "Review failed - please address findings" exit 1fiReviewing Specific Commits
Use --since to review commits since a specific point:
roborev review --since HEAD~5 # Review last 5 commitsroborev review --since abc123 # Review commits since abc123 (exclusive)roborev review --since v1.0.0 # Review commits since a tagThe range is exclusive of the starting commit (like git’s .. range syntax). Unlike --branch, this works on any branch including main.
Large Diffs
For --dirty reviews, diffs are limited to 200KB since uncommitted changes cannot be easily inspected by the agent. If your dirty diff exceeds this limit, commit your changes in smaller chunks.
For committed changes, diffs over 250KB are omitted from the prompt - the agent is given only the commit hash and can inspect changes using git show.
See Also
- Reviewing Branches - Review entire feature branches
- Commands Reference - Full command list