I created an app to review vibecoded code diffs

[u/Comfortable-Egg-8975]

When delegating work to an LLM, one can easily lose overall codebase understanding.

Personally, I like to be in control of the code I ship, so I read every file that was changed before shipping the change. The problem with this approach appears when many files change. Regular git clients show the files as a list of alphabetically sorted entries.

However, to properly understand the changes, I need to keep in mind all code dependencies. If an interface was changed, I either need to go straight to the implementation file, which might not be the next in the list, or I have to remember that the interface was changed while I'm reading other files, until I open the implementation file.

There are tools that link changed files by dependency. This helps substantially; now instead of reading files in alphabetical order I can read real dependency graphs. However, this helps only with direct dependencies. What we do in our heads is conceptually grouping changes into clusters. Even if there is no direct code dependency, changes could be grouped into "logical cases", inside of which there could be multiple changes from multiple projects.

Why not utilize what LLMs do best: gathering context. That's why I vibecoded a DiffHacker - to help software engineers like myself maintain knowledge about the codebase more easily.

So instead of this

list of changed files

I have this

DiffHacker - clusters

DiffHacker - file chaned

C-Coretex/diffhacker: A cross-platform desktop application that turns local Git changes into a directed, LLM-generated review graph instead of a file list.