AI-powered code review using CodeRabbit CLI and GitHub integration. Use when running local code reviews before commits ("run coderabbit", "review my changes"), configuring .coderabbit.yaml files, integrating CodeRabbit with Claude Code for autonomous review workflows, using @coderabbitai commands in pull requests, or setting up automated code review pipelines.
Runs CodeRabbit CLI to perform AI-powered code reviews that catch race conditions, memory leaks, and security vulnerabilities. Use when you need comprehensive code analysis before commits or as part of automated review workflows.
/plugin marketplace add basher83/lunar-claude/plugin install claude-dev-sandbox@lunar-claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/claude-code-integration.mdreferences/configuration.mdreferences/github-commands.mdreferences/overview.mdreferences/tools-reference.mdreferences/yaml-configuration-guide.mdAI code review tool that catches race conditions, memory leaks, and security vulnerabilities. Integrates with Claude Code for autonomous review-and-fix workflows.
Run CodeRabbit as part of your development workflow:
Implement the feature from the spec, then run coderabbit --prompt-only
in the background and fix any issues found.
Key flags for Claude Code:
--prompt-only - Minimal output optimized for AI agents--plain - Plain text mode (no interactive UI)--type uncommitted - Review only uncommitted changes# Install
curl -fsSL https://cli.coderabbit.ai/install.sh | sh
# Authenticate (run once per Claude Code session)
coderabbit auth login
# Review code
coderabbit # Interactive mode
coderabbit --plain # Plain text output
coderabbit --prompt-only # AI-optimized output
coderabbit --type uncommitted # Only uncommitted changes
coderabbit --base develop # Compare against develop branch
Recommended prompt pattern:
Please implement [feature] and then run coderabbit --prompt-only,
let it run as long as it needs (run it in the background) and fix any issues.
CodeRabbit reviews take 7-30+ minutes. Run in background and check periodically.
Fix prioritization: Fix critical issues first, ignore nits. Run CodeRabbit again after fixes to verify no new issues introduced. Limit to 2 iterations.
Use @coderabbitai in PR comments:
| Command | Description |
|---|---|
@coderabbitai review | Incremental review of new changes |
@coderabbitai full review | Complete review from scratch |
@coderabbitai pause | Stop automatic reviews |
@coderabbitai resume | Restart reviews |
@coderabbitai summary | Regenerate PR summary |
@coderabbitai generate docstrings | Generate function docs (Pro) |
@coderabbitai generate unit tests | Generate tests (Pro) |
@coderabbitai resolve | Resolve all CR comments |
@coderabbitai configuration | Show current settings |
Add @coderabbitai ignore to PR description to disable reviews for that PR.
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
language: en-US
tone_instructions: "Be concise and focus on critical issues only"
reviews:
profile: chill # or "assertive" for comprehensive feedback
high_level_summary: true
auto_review:
enabled: true
drafts: false
ignore_title_keywords:
- "wip"
- "draft"
knowledge_base:
code_guidelines:
enabled: true
filePatterns:
- "**/.cursorrules"
- "**/claude.md"
CodeRabbit auto-reads claude.md and .cursorrules for coding standards.
CodeRabbit integrates 40+ linters and security analyzers:
Full tools reference: See references/tools-reference.md
CodeRabbit not finding issues:
coderabbit auth statusgit status--type uncommitted--base developClaude Code not applying fixes:
--prompt-only modeThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.