Show HN: Codiff, a local diff review tool(github.com)
21 pointsby cpojer6 hours ago9 comments
  • magnio4 hours ago
    Is diff viewer the 2026 todo list?

    List of vibe coded alternatives:

    - revdiff: https://github.com/umputun/revdiff

    - hunk: https://github.com/modem-dev/hunk

    - diffnav: https://github.com/dlvhdr/diffnav

    - diffx: https://github.com/wong2/diffx

    - lumen: https://github.com/jnsahaj/lumen

    • cpojer4 hours ago
      4 of these are TUIs. I built Codiff specifically because TUI review became overwhelming to me. One of them is a web view, I prefer a native app window (it’s JS either way, ofc).

      Also, I never wasted time building todo apps. Now I can build apps that help me do my job that I wouldn’t have had the time for without AI.

      • bestouff3 hours ago
        Kids these days. Calling JS "native" makes my stomach ache, but apparently this is normal.
        • cpojer2 hours ago
          1. I’m older than you. 2. I said native app window, comparing it to a tool with a browser web ui.
    • stephenr3 hours ago
      [dead]
  • realrocker4 hours ago
    :) We are all converging on the same problems and tooling to fix them.

    Built this in the last couple days to review changes done by claude on a hetzner box(over tailscale on my phone) and leave comments before pushing to remote : https://github.com/livetemplate/prereview.

    Runs everywhere and can has a claude skill: /prereview which starts a new instance for the current changes. Has a “Hand-off” button to signal claude to process the comments.

    UI is responsive. I use it on my iphone with claude mobile app + /remote-control to leave comments before pushing.Still requires polish but core features work.

    • cpojer4 hours ago
      That’s awesome! I built this specifically as a GUI because it’s become too much code to effectively review in the terminal for me.
      • realrocker4 hours ago
        exactly. LLM code output is so high that it has become unreasonable to review the code in terminal or ide
    • Evan-Purkhiser4 hours ago
      Would love to see some screenshots in your readme of this!
      • realrocker4 hours ago
        Yeah the project is right out of the oven so will add some usage gifs shortly to the repo. Meanwhile here are some screenshots on imgur: https://imgur.com/a/zxZo651
  • tcoff914 hours ago
    Can you include screenshots in your readme?

    Also does it only work for staging and unstaged changes? I use jj so I need to be able to point it at commits since jj has no staging it just creates a new git commit snapshot every time you run any jj command.

    • cpojer4 hours ago
      There is a screenshot in the README.

      There is a video here: https://x.com/cnakazawa/status/2055881241677668637?s=46&t=BS...

      It works for any staged, unstaged or untracked file in a repo. It does not have support for mutations (like staging or unstaging a change) yet. It does not yet work for specific commits but should be super easy to add.

  • sjhalani76 hours ago
    That's awesome. Been reviewing code diffs on the IDE and it's been hard, so will check this out!
  • usernametaken295 hours ago
    Surprisingly enough this has just a few features the JetBrains diff view is lacking, notably file search… good ideas
  • stephenr4 hours ago
    Who knew that the killer task for LLMs would be "recreate existing things that exist without me mentioning them by name, based on a worse alternative as the example".

    Kaleidoscope exists.

    File Merge exists.

    • cpojer4 hours ago
      Codiff is faster and scales to larger commits than those.
      • stephenr3 hours ago
        You're seriously suggesting that an electron app you vibe coded in two days is more performant than native code that's been developed and improved and tweaked over literal decades?
        • cpojer3 hours ago
          Yes. It’s built on diffs.com and trees.software.
  • atmanactive5 hours ago
    ... for MacOS.
  • xiaosong0014 hours ago
    [flagged]
  • amys94fr4 hours ago
    [dead]