Personally speaking the git diff command is great for output, but can be improved for reviewing.

With difi the TUI made for git diff it allows to me speed up the review process and make it more enjoyable.

For the nvim integration, there already exists diffview and code diff, but I still favors the github website's solution of highlighting + and - inside one file rather then side by side.

difi: https://github.com/oug-t/difi difi.nvim: https://github.com/oug-t/difi.nvim

Reminds me of `tig`, which is a TUI with a continuous diff (not side by side) viewer… you can revert chunks inline. Has tree view, diff view and blame view.

One recommendation to help this tool gain traction: use a black and white terminal for your terminal preview (GIF).

1. It will ease reading. It's currently terrible, you might be used to it but we aren't.

2. It will sharpen the text and make it easier to read since there's less to encode into the GIF format.

Additional recommendations: remove the useless part on the right—I use Arch BTW vibe—and make the font bigger.

Looks like a neat tool, and one I really need! I actually started building my own because I couldn't find anything satisfying. My build is currently in the very early stages and I'd love to abandon it :-) I'm definitely going to try difi out.

Also kudos for putting up a screenshot. I've looked through a lot of projects claiming to do similar to this, but there are so many different interpretations that can make it not a good fit for me, and when there aren't any screenshots the barrier of seeing it in action is often too high to where I only try one or two before I give up and stop wasting time. Having a screenshot made it so I could check it out quickly.

The screenshot is a little rough, so a few tips for next time:

1. Shrink your terminal window down a bit as a huge view is harder to follow

2. Keep the screenshots at full resolution so they are easier to read. The reduced resolution and the original screen being huge makes the text pretty difficult to read, even zoomed in to 200%

3. Use something like screenkey (or throw some subtitle text up or something) so the viewer knows what keys you are pressing and/or what you're trying do. It's pretty hard to follow along without those queues.

Great work, and thanks for sharing!