# where hunk fits

Hunk vs the tools
you already run.

Most terminal diff tools are pagers. They restyle the text Git already printed. Hunk is a review UI: one multi-file stream, a file sidebar, split and stack layouts, expandable context, watch mode, and agent notes beside the code. These pages say where that is worth it, and where the other tool wins.

5 comparisons ยท checked against each project's own docs in September 2026

Hunk vs deltadelta restyles the text Git already printed. Hunk turns the same changeset into a review UI. Most people keep both.Hunk vs difftasticdifftastic changes what the diff says. Hunk changes how you read the changeset. Different problems, both worth solving.Hunk vs diff-so-fancydiff-so-fancy tidies Git's diff output. Hunk replaces the reading experience. The gap is bigger than it looks.Hunk vs git diffgit diff prints the patch. Hunk renders the same patch as something you can navigate. Git stays the source of truth.Hunk vs PlannotatorBoth exist because agents write more code than you can read. Plannotator reviews it in the browser and covers plans. Hunk stays in the terminal.

How these are written

Every mark comes from the other project's own docs. Where a bare mark would mislead, the caveat sits next to it. Rows the other tool wins are in the tables too: structural diffing, styled git blame, plan review before code exists. A comparison that concedes nothing is not worth reading.

Each page is also served as Markdown at the same URL plus .md, and its capability table is published as JSON-LD, so an agent can read the comparison without parsing the layout. The docs corpus is available the same way at /llms.txt.

Try Hunk on your next changeset.

Install hunkRead the quick start