Skip to main content
A PR often changes several files to do one thing. cubic groups those files together and orders them for review, so you can follow the change across the codebase. For example, a PR that adds coupon codes to checkout might change a coupon lookup, the pricing math, a checkout API, and a checkout page. cubic puts the lookup and pricing first, then the API, then the page, so each group builds on the one before it. The Coupon Lookup Logic group with its explanation and diff, beside a file list of four groups in review order

​
Follow the review order

In the Changes tab, choose Grouped at the top of the file list. Each group has a name that describes the change. Open a file to jump to its diff, or read through the group in order. cubic orders the groups, and the files in each group, for a first read. Code that defines behavior, such as schema changes, API contracts, and core logic, comes first. Tests and generated files such as lockfiles usually come later.

​
Read the explanations

Each group starts with an explanation of what changed and how its files fit together. To jump to the code, click a function or type name in the explanation. For a deeper walkthrough, ask AI chat to “tour this PR”. The tour follows the review order, opens each file, and explains what to check.

​
Track your progress

When you finish reading a file, mark it Viewed. After you’ve read every file in a group, mark the group Reviewed.

​
Browse by folder

To see the changed files in their directory structure, switch to Tree. You can also search the file list to jump to a file by name. To focus on the implementation, choose Diff settings > Hide test files from the PR actions menu. Show the tests again when you’re ready to review them.