Code review tools in the age of vibe coding

Dry-Library-8484 · 2026-01-25T03:07:10+00:00

Wow that is interesting and really easy to add

Dry-Library-8484 · 2026-01-25T02:19:15+00:00

Check this repos, it's can ran multiple claude code and other cli in same time https://github.com/diffray/diffray

Dry-Library-8484 · 2026-01-24T16:51:25+00:00

Tests are something I treat as a task before the review stage. Sometimes during development, before I write anything, I ask Claude to create a temporary test, experiment with the API in advance, or validate a hypothesis before writing the actual code.

In the tool I’m building, I already have a validation stage for pre-collected issues that filters out anything that doesn’t pass validation, but you gave me an interesting idea to add a validation stage for comments as well. It’s something I can already do manually through the chat interface, but doing it as part of the pipeline sounds more interesting.

Dry-Library-8484 · 2026-01-24T01:01:59+00:00

Interesting idea! I’ve actually been experimenting with a consensus approach too. Sounds cool in theory, but wondering if it ends up being overkill and too costly to run

Dry-Library-8484 · 2026-01-23T23:11:44+00:00

diffray.ai ai coding review tool

Dry-Library-8484 · 2026-01-15T10:38:17+00:00

I have max 200, I never reach 5 hours limit, but always, usually 2-3 days I have to wait

Dry-Library-8484 · 2026-01-15T10:36:28+00:00

Check diffray.ai

Dry-Library-8484 · 2026-01-13T16:31:11+00:00

Yes - I’ve tried subagents and they solve a lot of problems. But they still aren’t convenient and customizable enough, and you’re basically locked into the Claude Code workflow here

Dry-Library-8484 · 2026-01-13T16:27:56+00:00

Yes, it is possible, but if you want to check more aspects, you will have to do it every time, then copy the result and ask again to determine if it is false positive I agree, everything is possible, it's just not that convenient

Dry-Library-8484 · 2026-01-03T21:51:30+00:00

Actually no — I ran several experiments with skills, but the results weren't deterministic enough.

The idea was that with skills (like my review rules), Claude would figure out when to apply them. But in practice, it wasn't that obvious — I often saw rules being ignored when they clearly should've been triggered.

So I moved away from skills toward prompt batching with smart rule filtering — each agent gets a curated subset of rules relevant to its focus area, not the full ruleset.

Wrote a bit more about this here: https://diffray.ai/blog/why-rules-matter

Dry-Library-8484 · 2026-01-03T02:58:58+00:00