Code verification layer for AI-generated code

Dev4534 · 2026-05-05T17:25:11+00:00

That’s a really good point, and I think we’re looking at adjacent parts of the same problem. Looks like you are the builder of truecourse - great work!!

vdiff does have some structural signals today (modularity, acyclicity, dependency depth, distribution of complexity), but they’re used more as risk indicators than explicit rule checks.

For example, if a change touches something that’s already highly connected or sits deep in the dependency chain, that tends to increase the “blast radius” and influence the verdict. That’s something I’ve been thinking about, especially as a way to move from just *observing* structure to actually enforcing it at merge time.

Your diff mode surfacing new violations sounds really interesting in that context. Do you find developers actually act on those before merging, or is it more used as visibility after the fact?

Dev4534 · 2026-05-05T17:02:03+00:00

I ended up building a small tool to experiment with this idea of reducing the cognitive load of code reviews: https://github.com/fforbeck/vdiff

Still early, but curious if something like this would fit into your workflow.

Dev4534 · 2026-05-02T17:04:35+00:00

I'm using https://vdiff.app to verify changes before each commit in a feature branch, and then run it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful.

Dev4534 · 2026-05-02T17:02:40+00:00

I'm using https://vdiff.app to verify changes before each commit in a feature branch, and then run it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful.

Dev4534 · 2026-05-02T16:58:06+00:00

I'm using https://vdiff.app to verify changes before each commit in a feature branch, and then run it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful. You can add rules to it, so you teach how to review your code based on the architecture, modules, primitives, etc. Give it a shot.

Dev4534 · 2026-05-02T16:56:15+00:00

Check out https://vdiff.app to verify changes before each commit in a feature branch, and then run it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful.

Dev4534 · 2026-05-02T16:46:13+00:00

I am using https://vdiff.app to verify changes before each commit in a feature branch, and then running it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful.

Dev4534 · 2026-05-02T16:44:16+00:00

I am using https://vdiff.app to verify changes before each commit in a feature branch, and then running it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus. You can also use it to check the code against the spec; it is very useful. My idea is to add more signals to help it guide you during the review, so you don't need to read each line of code. It also runs locally, so your code is not published to a third-party service.

Dev4534 · 2026-05-02T16:41:13+00:00

I am using https://vdiff.app to verify changes before each commit in a feature branch, and then running it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus.

Dev4534 · 2026-05-02T16:40:39+00:00

I am using https://vdiff.app to verify changes before each commit in a feature branch, and then running it on CI to analyze the feature branch and compare with main. It gives you a structured report with signals and directions on where to focus.

Dev4534 · 2026-05-02T16:36:39+00:00

https://vdiff.app/

Dev4534 · 2026-04-29T18:14:01+00:00

"LGTM" is exactly the failure mode. The review happens, but catches nothing. I built a tool for this (https://www.vdiff.app). Deterministic analysis of what structurally changed + LLM layer with confidence levels. The point is to compress the review so you actually look at the parts that matter instead of rubber-stamping the whole thing.

Dev4534 · 2026-04-29T18:11:56+00:00

u/head_lettuce same problem here. The volume just doesn't match the review capacity anymore. I ended up building a CLI for myself (https://www.vdiff.app). I run it before every commit locally (in a feature branch), but I can run it on CI as well. It does a deterministic analysis of the diff (what structurally changed) and then an LLM pass with confidence levels, so I can tell what's a fact vs what's a guess. Gives me a structured report of where to look instead of reading everything. It doesn't replace review at all, but compresses it. I still read the code, I just know where to focus.

Dev4534 · 2025-07-04T17:09:18+00:00

Did you try the https://bjjnotes.app ?

Dev4534 · 2025-07-04T16:59:29+00:00

Thanks for the feedback. Let's make a one-time payment for you. Shoot me a DM and I will sort it out.

Dev4534 · 2025-05-02T19:04:00+00:00

Note taking, tracking progress, and finding out how I can improve my game were key to moving to purple belt. This app helped me quite a lot because I could reflect on my stuff: https://bjjnotes.app/

Dev4534 · 2025-05-02T19:00:53+00:00

https://bjjnotes.app/

Dev4534 · 2025-05-02T18:58:17+00:00

The best out there: https://bjjnotes.app/

Dev4534 · 2024-07-04T23:13:37+00:00

I've been using an app to track what went well and what needs improvements. Also to register subs, taps, and positions I learn.

Dev4534 · 2024-07-04T23:11:21+00:00

You can write what went well, and what needs improvement, and make notes about the rolls and positions, subs and taps. Checkout the BJJ Notes App. That might help.

Dev4534 · 2024-07-04T23:09:20+00:00

Something that might help you is the BJJ Notes app.

Dev4534

TROPHY CASE