The review loop

Review, rework, re-review. Step through the laps and watch findings shrink — until the cap decides what happens next.

The problem this replaces

Review → done, no re-check

The fix was never re-reviewed. Nobody checked whether "fixed" actually was.

How it works

Same three steps every lap. The number of laps is capped, so it can't spin forever.

Most changes clear well before the cap. The cap exists for the rare case that doesn't — so it lands on a person, not in an infinite loop.

See it in action

review: 1 finding — missing loading state → rework: state added → re-review: 0 findings → cleared, lap 1

Most changes never see lap two.

So what

It won't argue with itself forever — a stuck change reaches you.