Configure CodeRabbit CLI for local pre-commit code reviews and fast iteration. Use when setting up local development with CodeRabbit CLI reviews, integrating AI review into your commit workflow, or testing config changes. Trigger with phrases like "coderabbit dev setup", "coderabbit local development", "coderabbit CLI workflow", "coderabbit pre-commit review".
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Use CodeRabbit CLI to review code locally before opening a PR. The CLI provides the same AI-powered review as the GitHub App but runs in your terminal against staged or unstaged changes. This creates a multi-layered review process: local CLI review before commit, then automated PR review after push.
curl -fsSL https://cli.coderabbit.ai/install.sh | sh).coderabbit.yaml configurationset -euo pipefail
# Install CodeRabbit CLI
curl -fsSL https://cli.coderabbit.ai/install.sh | sh
# Verify installation
cr --version
# Authenticate (opens browser for OAuth)
cr auth loginset -euo pipefail
# Review all staged changes (most common workflow)
git add -A
cr review
# Review specific files only
cr review src/api/routes.ts src/middleware/auth.ts
# Interactive mode: ask follow-up questions about review feedback
cr review --interactive
# Plain output mode (pipe to other tools or AI agents)
cr review --prompt-only#!/bin/bash
# .git/hooks/pre-push (make executable: chmod +x .git/hooks/pre-push)
set -euo pipefail
echo "Running CodeRabbit pre-push review..."
# Get list of changed files vs remote
CHANGED_FILES=$(git diff --name-only @{push}.. 2>/dev/null || git diff --name-only HEAD~1)
if [ -n "$CHANGED_FILES" ]; then
echo "$CHANGED_FILES" | xargs cr review
# Non-blocking: show review but don't prevent push
# To make blocking, check exit code:
# echo "$CHANGED_FILES" | xargs cr review || {
# echo "CodeRabbit found issues. Push anyway? (y/n)"
# read -r response
# [ "$response" != "y" ] && exit 1
# }
fi# .coderabbit.yaml - Settings that affect both CLI and PR reviews
language: "en-US"
reviews:
profile: "assertive"
path_instructions:
- path: "src/**"
instructions: "Check for proper error handling and type safety."
- path: "tests/**"
instructions: "Verify edge cases and assertion completeness."
path_filters:
- "!**/*.lock"
- "!dist/**"
- "!**/*.generated.*"
auto_review:
enabled: true
drafts: false
chat:
auto_reply: true// .vscode/tasks.json - Run CodeRabbit review from VS Code
{
"version": "2.0.0",
"tasks": [
{
"label": "CodeRabbit: Review Current File",
"type": "shell",
"command": "cr review ${file}",
"presentation": { "reveal": "always", "panel": "shared" },
"problemMatcher": []
},
{
"label": "CodeRabbit: Review Staged Changes",
"type": "shell",
"command": "cr review",
"presentation": { "reveal": "always", "panel": "shared" },
"problemMatcher": []
}
]
}Developer writes code
│
▼
┌──────────────────┐
│ cr review (local) │ ← Layer 1: Fast feedback before commit
│ Fix obvious issues│
└────────┬─────────┘
│
▼
git commit + push
│
▼
┌──────────────────┐
│ CodeRabbit App │ ← Layer 2: Full context review on PR
│ (automated PR │
│ review) │
└──────────────────┘| Issue | Cause | Solution |
|---|---|---|
cr: command not found | CLI not in PATH | Re-run install script or add to PATH |
| Auth token expired | Session timeout | Run cr auth login again |
| "No credits remaining" | Usage-based billing exhausted | Purchase credits at app.coderabbit.ai |
| Review hangs on large file | File too large for AI context | Review specific files instead of all |
| Empty review output | No changed files detected | Stage changes with git add first |
See coderabbit-sdk-patterns for PR interaction automation patterns.
3a2d27d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.