Skip to content

Files

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Latest commit

d6ff746 · May 21, 2025

History

History
42 lines (29 loc) · 1.62 KB

code-review-best-practices.md

File metadata and controls

42 lines (29 loc) · 1.62 KB
title description sidebar_label
Code review best practices
Best practices for managing CodeRabbit code reviews.
Best practices

This page lists best practices for performing code reviews with CodeRabbit.

For more information about working with CodeRabbit through chat, see Control and manage code reviews.

For a CodeRabbit command reference, see Code review command reference.

Recommended code-review workflow

  • Start with @coderabbitai review for checking new changes.
  • Use @coderabbitai full review when major changes require a fresh perspective.
  • Generate summaries after significant updates using @coderabbitai summary.

Managing large changes

  • Use @coderabbitai pause before making multiple commits.
  • Resume reviews with @coderabbitai resume when ready.
  • Consider @coderabbitai full review after substantial changes.

Documentation flow

  • Run @coderabbitai generate docstrings after finalizing function implementations.
  • Learn more about docstring generation.

Overall tips

  • Commands are case-insensitive (@coderabbitai REVIEW works the same as @coderabbitai review).
  • Commands can be issued by anyone with write access to the repository.
  • Multiple commands can be used in sequence as needed.
  • Use @coderabbitai configuration to export your settings before making changes.

Command response time

  • Most commands (pause, resume, ignore) take effect immediately.
  • Review commands typically complete within a few minutes, depending on PR size.
  • Docstring generation time varies based on the number of functions.