coderabbit-performance-tuning

CodeRabbit Review Performance Tuning

Overview

Optimize operator-controlled inputs and measure effects. Separate service latency, provider delay, limits, diff size, paths, tools, and guidance.

Prerequisites

• Identify the CodeRabbit organization, Git provider, repository, plan, and accountable owner.
• Read references/official-docs.md and re-check any time-sensitive contract before execution.
• Use synthetic or read-only evidence until the approval boundary is satisfied.
• Preserve the repository's independent CI, security, and human-review requirements.

Current Contract

• Path filters change scope; path instructions change guidance.
• Incremental reviews can pause after configured reviewed commits.
• Caching normally accelerates review but can be disabled.
• Plan limits belong to the live plans contract.

Authentication

Treat Git-provider sessions, CodeRabbit web sessions, CLI credentials, and CodeRabbit API keys as separate credentials. Use only an already-approved session or secret-manager reference, never print a secret, and do not place credentials in .coderabbit.yaml, source files, logs, or deliverables.

Instructions

1. Capture events, files, diff size, tools, cache, limits, findings, and timing.

2. Classify delay or noise by boundary.

3. Pilot one scope, filter, instruction, profile, or incremental-review change.

4. Compare equivalent samples and roll back hidden-risk regressions.

Tool Discipline

• Use Glob to locate candidate configuration and evidence files without widening scope.
• Use Grep to find relevant fields, commands, identifiers, and stale claims.
• Use Read to inspect the smallest required files and authoritative evidence.
• Use Write only for a new approved local draft or evidence artifact.
• Use Edit only for a bounded approved change whose rollback is known.
• Do not use these file tools as a substitute for authenticated CodeRabbit or provider operations.

Approval Boundaries

Require security or code-owner approval before exclusions, tool disablement, or shared changes. Keep analysis and drafts local until approval is explicit, and record who approved the action and its scope.

Output

A baseline, hypothesis, patch, comparison, risk check, and keep-or-rollback decision. Include source dates, unknowns, and the exact boundary between observed fact and recommendation.

Error Handling

Examples

Example 1

Exclude generated artifacts while retaining sensitive code.

Example 2

Tune incremental-review pause for a high-churn branch.

Validation

• Confirm every claim against the dated sources in references/official-docs.md.
• Verify the requested scope, owner, approval, happy path, failure path, and rollback.
• Re-read the effective configuration or provider state after any approved change.
• Report unsupported fields, undocumented endpoints, and unverified assumptions as failures.

Resources

• Official documentation and contract notes
• Re-check the dated contract before any live operation.
• Treat unresolved or changed vendor behavior as a stop condition.