Skip to main content
|

​
Overview

Change Stack is CodeRabbit’s PR inspection interface. It takes any pull request and reorganizes it into a small number of independent change cohorts, logical groupings of related work, each broken into ordered layers that reflect the natural reading order of the change. Every layer anchors to specific line ranges in the diff, each with its own summary. Reviewers open Change Stack from the Review Change Stack → button that CodeRabbit posts in the comment. Inside, they navigate cohorts and layers with the keyboard. On GitHub, GitLab, and Bitbucket, they can also drop inline comments against specific ranges and submit native review feedback without leaving the Change Stack tab.
Change Stack is available on GitHub Cloud, GitHub Enterprise Server, GitLab.com, self-managed GitLab, Bitbucket Cloud, Bitbucket Data Center, and Azure DevOps. Azure DevOps support is read-only during early access; inline commenting and review submission are not yet supported. Change Stack is in early access and is available to all users during launch. It will be part of the Pro+ plan going forward.

​
Why Change Stack

AI-assisted development has made pull requests larger and more frequent; a single AI-authored change can touch dozens of files across multiple layers of a codebase. A git provider’s or IDE’s default diff view can present those files alphabetically without reflecting the logical dependencies between them. Change Stack reorganizes the diff into cohorts and layers that reflect the structure of the change:
  • Cohorts group related files and hunks that belong together conceptually.
  • Layers order those groups so foundational changes (data shapes, contracts) come before the code that depends on them (consumers, call sites, tests).
  • Range summaries explain each contiguous block of changed lines in plain language.
  • Diagrams are generated inline for layers where a visual earns its place, such as sequence diagrams for new call flows, state machines for lifecycle changes, and ERDs for data model updates. Layers that do not warrant a diagram do not get one.

​
Opening Change Stack

Every pull request review comment from CodeRabbit includes a Review Change Stack → button above the standard walkthrough. Clicking it opens the review in the Change Stack interface.
CodeRabbit review comment showing the Review Change Stack button alongside Walkthrough and Pre-merge checks sections

"Review Change Stack →" button in the CodeRabbit review comment

Change Stack is opt-in per reviewer. Teammates who prefer their git provider’s default review experience can ignore the button. Nothing about the PR workflow changes for them.

​
The three-panel layout

Change Stack uses a fixed three-panel layout tuned for rapid navigation: