code-rabbit

CodeRabbit Review Handler

Process CodeRabbit review comments with context-aware discretion.

Usage

/code-rabbit

Then paste one or more CodeRabbit comments.

Instructions

1. Initial Context

Inform the user:

I'll review the CodeRabbit comments with discretion, as CodeRabbit doesn't have access to the entire codebase and may not understand the full context.

For each comment, I'll:
- Evaluate if it's valid given our codebase context
- Accept suggestions that improve code quality
- Ignore suggestions that don't apply to our architecture
- Explain my reasoning for accept/ignore decisions

2. Process Comments

Single File Comments

If all comments relate to one file:

• Read the file for context
• Evaluate each suggestion
• Apply accepted changes in batch using MultiEdit
• Report which suggestions were accepted/ignored and why

Multiple File Comments

If comments span multiple files:

Launch parallel sub-agents using Task tool:

Task:
  description: "CodeRabbit fixes for {filename}"
  subagent_type: "general-purpose"
  prompt: |
    Review and apply CodeRabbit suggestions for {filename}.
    
    Comments to evaluate:
    {relevant_comments_for_this_file}
    
    Instructions:
    1. Read the file to understand context
    2. For each suggestion:
       - Evaluate validity given codebase patterns
       - Accept if it improves quality/correctness
       - Ignore if not applicable
    3. Apply accepted changes using Edit/MultiEdit
    4. Return summary:
       - Accepted: {list with reasons}
       - Ignored: {list with reasons}
       - Changes made: {brief description}
    
    Use discretion - CodeRabbit lacks full context.

3. Consolidate Results

After all sub-agents complete:

📋 CodeRabbit Review Summary

Files Processed: {count}

Accepted Suggestions:
  {file}: {changes_made}
  
Ignored Suggestions:
  {file}: {reason_ignored}

Overall: {X}/{Y} suggestions applied

4. Common Patterns to Ignore

• Style preferences that conflict with project conventions
• Generic best practices that don't apply to our specific use case
• Performance optimizations for code that isn't performance-critical
• Accessibility suggestions for internal tools
• Security warnings for already-validated patterns
• Import reorganization that would break our structure