Reviewing in the time you actually have

The problem

“I will read it properly later” is where review goes to die. Without a budget every pull request is read the same way: skimmed from the top until attention runs out, which is rarely where the risk is.

What visualdiff does

• Set a time budget per review. The plan sorts every hunk into read, skim or skip so that what matters fits the minutes you have.
• Each item says why it is there: new code, high fan-in, a finding, a sensitive area. Each skip says why it is safe to skip.
• A reading order follows the dependencies, so the twenty minutes are spent in the order that builds understanding.