Diffs that show what changed, not just which lines.
Sailfork marks the words that changed inside a line, follows code that moved, and draws tables, notebooks and images as what they are.
src/billing/invoice.ts
src/billing/retry.ts
Try the engine
Edit either side. The diff below comes from the same Rust code that diffs every pull request on Sailfork, running in your browser.
Loading the diff engine…
See it on a real pull request
Pull request #1 of sailfork/diff-demo, a public repository, as the engine draws it. Open it and review it the way your team would.
Charge for quantities and share the retry policy #1
11 files +44 −24
- Changed ci.yml CI workflow +2 −2
- Changed stock.csv +3 −3
- Added 0002_payment_attempts.sql Migration +7 −0
- Changed forecast.ipynb +4 −3
- Renamed from src/util/money.ts money.ts +2 −0
- Changed invoice.ts +3 −3
- Added retry.ts +8 −0
- Changed cart.ts +7 −2
- Changed pay.ts +4 −8
- Changed billing.md +2 −2
- Changed package.json +2 −1
Packages: 1 updated, 1 added
- p-retry added 6.2.1
- zod 3.23.8 → 3.24.1
The words that changed, marked inside the line
A one-character fix reads as one character, not two whole lines to compare by eye.
Code that moved says where it went
Both ends link to each other, so a move is not reviewed twice as a delete and an add.
src/checkout/pay.ts:40 src/billing/retry.ts:8 4 lines, found across files
A block cut from one file and pasted in another is found across files and hunks, even when its indentation changed or it was edited on the way.
Made for the pull requests agents open
Vite 5.0.0 to 5.4.0 in one pull request: 173 files, with vendored code folded until you open it.
Renames are followed
A file renamed with edits is found at 50% similarity, and its history follows it.Formatting folds away
Runs that only re-lay out the same code fold by default; in Python or YAML, indentation is never folded.Generated files start folded
Lockfiles, minified files and anything .gitattributes marks generated stay closed until you open them.The first lines arrive with the page
The first 2,000 changed lines come with the page; the rest load as you scroll.Only what is on screen is drawn
A long diff keeps the rows you see and drops the rest, so scrolling stays smooth.A suggested reading order
Code first, then tests, docs and generated files, each file ahead of the files that import it.
Fast on the server, light in the browser
The server works out the whole diff, the changed words in every line and the code that moved before the page asks.
| Change | Files | Changed lines | Diff | Moved code |
|---|---|---|---|---|
| All of Vite added to a small service | 229 | 41,787 | 75.7 ms | 55.4 ms |
| Vite upgraded from 5.0.0 to 5.4.0 | 173 | 14,112 | 109.3 ms | 87.5 ms |
| A feature pull request | 11 | 68 | 20.2 ms | 8 ms |
Server time from the production API’s own timing header, the first time each range was asked for, on 2026-11-14. Repeat reads of the same commits come back in under 2 ms. Every range is in the public sailfork/diff-demo repository.
Risky files are named before you merge
Whatever the diff says, these files get a badge in the diff and a line in the merge checklist.
- SecretsKeys and passwords committed here are readable by everyone with access, and stay in the history after they are removed.
- CI workflowWorkflows run with the repository’s secrets and deploy rights.
- ContainerBase images and build steps decide what runs in production.
- Code ownersThis decides who must review future changes.
- MigrationIt adds a migration, and a migration never merges without a person.
- InfrastructureThese files describe servers, networks and access.
Review from the keyboard
Select lines by dragging the gutter or with the keyboard, and link straight to a line range. Files and hunks you mark viewed stay marked.
j k
Next and previous filev
Mark the file viewedw
Wrap long linesShift F10
Comment, suggest or copy a link from the line menu


