Pull requests change a lot after they’re opened.

Sometimes it’s small stuff: fix a bug a reviewer caught, address a nit, rename a thing. Sometimes it’s bigger: you change the approach halfway through.

Two problems show up over and over:

• You introduce a new bug in the follow-up commits while fixing the original one

• The PR description stops matching what the code actually does

Today we’re shipping incremental PR checks and PR description updates to handle both.

What’s launching

When you push new commits to an open PR, cubic now:

1. Reviews the incremental changes

   It looks at what changed since the last push and comments only on new issues introduced by those changes.

2. Updates the PR description when necessary

   If the PR’s intent changed in a meaningful way, cubic updates the PR description so it matches the current state of the code.

Details

We’ve been running this quietly and rolling it out gradually. It’s now generally available. Noise has been top of mind. A lot of teams like cubic because it stays clean and minimal. We want to keep that. So the behavior is simple:

• If cubic finds issues in the incremental changes, it comments

• If it finds nothing, it leaves nothing. You just get a green check

Why this matters

A lot of review time is wasted rereading the same PR over and over because a few commits landed since the last look.

Incremental checks keep reviewers oriented, and keeping the description in sync removes a whole category of confusion.

Enable incremental reviews in your cubic settings → https://www.cubic.dev/sign-up