CodeRabbit Code Review

Philosophy

• Treat CodeRabbit as a risk amplifier: prioritize critical and warning findings first.
• Keep review output actionable and linked to changed files.
• Iterate review and fixes until high-risk findings are resolved or explicitly deferred.

When to use

• User requests CodeRabbit review for current repo changes.
• User wants a quality or security sweep before push/merge.
• User asks for an autonomous build-review-fix cycle using CodeRabbit CLI output.

Inputs

• change_scope: all, committed, or uncommitted diff target.
• base_reference: optional base branch or commit.
• output_mode: prompt-only or plain output.
• auth_state: CodeRabbit CLI authentication status.