HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
flamestro
deff
Rust2026–2026
flamestro / deff

deff

interactive, side-by-side file review for git diffs with per-file navigation, vertical and horizontal scrolling, syntax highlighting, and added/deleted line tinting

2Distinct people
3Mentions
0Explicit recommenders
586GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

interactive, side-by-side file review for git diffs with per-file navigation, vertical and horizontal scrolling, syntax highlighting, and added/deleted line tinting

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2026-02-25 23:43:32 UTC to 2026-02-26 23:33:19 UTC.

012026-02-25 23:00:00 UTC to 2026-02-26 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 25, 23:002026-02-26 00:00:00 UTC to 2026-02-26 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 01:00:00 UTC to 2026-02-26 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 02:00:00 UTC to 2026-02-26 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 03:00:00 UTC to 2026-02-26 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 04:00:00 UTC to 2026-02-26 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 05:00:00 UTC to 2026-02-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 06:00:00 UTC to 2026-02-26 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 07:00:00 UTC to 2026-02-26 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 08:00:00 UTC to 2026-02-26 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 09:00:00 UTC to 2026-02-26 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 10:00:00 UTC to 2026-02-26 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 11:00:00 UTC to 2026-02-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 26, 11:002026-02-26 12:00:00 UTC to 2026-02-26 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 13:00:00 UTC to 2026-02-26 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 14:00:00 UTC to 2026-02-26 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 15:00:00 UTC to 2026-02-26 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 16:00:00 UTC to 2026-02-26 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 17:00:00 UTC to 2026-02-26 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-26 18:00:00 UTC to 2026-02-26 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 19:00:00 UTC to 2026-02-26 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 20:00:00 UTC to 2026-02-26 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 21:00:00 UTC to 2026-02-26 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 22:00:00 UTC to 2026-02-26 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-26 23:00:00 UTC to 2026-02-27 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 26, 23:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 25, 23:002026-02-25 23:00:00 UTC2026-02-26 00:00:00 UTC110
Feb 26, 00:002026-02-26 00:00:00 UTC2026-02-26 01:00:00 UTC000
Feb 26, 01:002026-02-26 01:00:00 UTC2026-02-26 02:00:00 UTC000
Feb 26, 02:002026-02-26 02:00:00 UTC2026-02-26 03:00:00 UTC000
Feb 26, 03:002026-02-26 03:00:00 UTC2026-02-26 04:00:00 UTC000
Feb 26, 04:002026-02-26 04:00:00 UTC2026-02-26 05:00:00 UTC000
Feb 26, 05:002026-02-26 05:00:00 UTC2026-02-26 06:00:00 UTC000
Feb 26, 06:002026-02-26 06:00:00 UTC2026-02-26 07:00:00 UTC000
Feb 26, 07:002026-02-26 07:00:00 UTC2026-02-26 08:00:00 UTC000
Feb 26, 08:002026-02-26 08:00:00 UTC2026-02-26 09:00:00 UTC000
Feb 26, 09:002026-02-26 09:00:00 UTC2026-02-26 10:00:00 UTC000
Feb 26, 10:002026-02-26 10:00:00 UTC2026-02-26 11:00:00 UTC000
Feb 26, 11:002026-02-26 11:00:00 UTC2026-02-26 12:00:00 UTC000
Feb 26, 12:002026-02-26 12:00:00 UTC2026-02-26 13:00:00 UTC000
Feb 26, 13:002026-02-26 13:00:00 UTC2026-02-26 14:00:00 UTC000
Feb 26, 14:002026-02-26 14:00:00 UTC2026-02-26 15:00:00 UTC000
Feb 26, 15:002026-02-26 15:00:00 UTC2026-02-26 16:00:00 UTC000
Feb 26, 16:002026-02-26 16:00:00 UTC2026-02-26 17:00:00 UTC000
Feb 26, 17:002026-02-26 17:00:00 UTC2026-02-26 18:00:00 UTC110
Feb 26, 18:002026-02-26 18:00:00 UTC2026-02-26 19:00:00 UTC000
Feb 26, 19:002026-02-26 19:00:00 UTC2026-02-26 20:00:00 UTC000
Feb 26, 20:002026-02-26 20:00:00 UTC2026-02-26 21:00:00 UTC000
Feb 26, 21:002026-02-26 21:00:00 UTC2026-02-26 22:00:00 UTC000
Feb 26, 22:002026-02-26 22:00:00 UTC2026-02-26 23:00:00 UTC000
Feb 26, 23:002026-02-26 23:00:00 UTC2026-02-27 00:00:00 UTC101

What Hacker News says

3 sources
You definitely need a gif or apng file showing it's use in the github readme. And a link to an asciicinema would help a lot too. --- Also, I'm not sure how useful the side-by-side view is. The second example (https://github.com/flamestro/deff/blob/main/docs/example_02....) is confusing. The left side has lines 1365-1371 having the same code as lines 1374-1380 on the right side, yet they're not aligned with each other. Most diff views would put padding between lines 1364-1365 on the left side so lines 1365-1371 are aligned with 1374-1380 on the right side.
In Show HN: Deff – Side-by-side Git diff review in your terminal
flamestro·Feb 26, 2026Submission

Show HN: Deff – Side-by-side Git diff review in your terminal

deff is an interactive Rust TUI for reviewing git diffs side-by-side with syntax highlighting and added/deleted line tinting. It supports keyboard/mouse navigation, vim-style motions, in-diff search (/, n, N), per-file reviewed toggles, and both upstream-based and explicit --base/--head comparisons. It can also include uncommitted + untracked files (--include-uncommitted) so you can review your working tree before committing. Would love to get some feedback
120 points · Open discussion
flamestro·Feb 25, 2026Submission

Show HN: Deff – Review AI-generated code changes

I built Deff because AI coding tools sped up writing code, but reviewing their changes became the new bottleneck. Most of my time was going into checking noisy diffs, understanding intent, and making sure nothing subtle broke. Deff is focused on one thing: helping you review AI-generated code changes faster and with more confidence. It helps surface what changed and is allowing me to use it with some vim motions so I can easily jump from nvim to opencode to deff. Would love feedback from people using AI coding assistants heavily — especially on review workflows, false positives, and what still feels slow.
1 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.