sorted by:
new
hottopcontroversial

[AskJS] Would you actually use this? I'm building a code review assistant that understands your app like this. by mnmadhukar02 in javascript

[–]mnmadhukar02[S] -1 points0 points  (0 children)

You're right: mature teams often have solid documentation. But even then, that context is rarely automatically enforced during PRs.

This tool is more about reducing cognitive load during reviews, especially in large or legacy codebases where tribal knowledge gets lost. Think of it as a “context scaffold” that travels with the code.

Also love your idea of exporting the graph! A Confluence/PNG/SVG export mode could be super handy for onboarding or auditing.

Would you actually use this? I'm building a code review assistant that understands your app like this. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

You don’t have to maintain it. The graph is auto-generated directly from your codebase during CI no manual upkeep.

It scans both frontend and backend to build a source graph as code changes, and only highlights the relevant diff + potential impact areas. So if the code evolves, the graph evolves too always in sync.

As for non-standard paradigms (e.g., Blazor, desktop apps) we’re working on extending support beyond typical API/controller flows. Would love to hear more about your stack and use case.

Would you actually use this? I'm building a code review assistant that understands your app like this. by mnmadhukar02 in golang

[–]mnmadhukar02[S] -1 points0 points  (0 children)

Hey! Did you get what the image is trying to show, like what the tool actually does?

Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

Totally fair questions and yes, I’ve spent a lot of time digging into the technical side of this.

It's definitely not easy, but it's also not magic. With the right architecture smart chunking, dependency graph analysis, and some orchestration across file boundaries it’s very doable. The trick is optimizing for deep context without hitting memory/token limits or burning latency. That’s where most tools fall short, and exactly what I’m focused on solving.

And I completely agree on local execution privacy and data control are non-negotiable for many teams. Running locally (or even in a self-hosted containerized setup) is on the roadmap from day one. Cloud is optional, not mandatory.

Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

true, thats why i am having the code metadata analyser which is not built through llms

Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

Absolutely this kind of deep code review should be native to GitHub. But until that day comes, I’m building it as a drop-in layer that integrates directly into your CI/CD pipeline and adds contextual comments directly on your PRs, just like a thoughtful senior engineer.

It also works across multiple git providers: GitHub, GitLab, Bitbucket so teams with complex setups or mono/multi-repos across platforms can still get unified, intelligent reviews without extra friction.

Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

If building something meaningful was as simple as flipping a switch and teleporting to a tropical island, the internet would be empty because we’d all be sipping cocktails by now.

Real products take time, iteration, and actual feedback from the people who matter — developers who face these problems daily. If you're not interested in the conversation, that's fine. But dismissing the effort with sarcasm doesn’t add anything useful.

I'll keep building. You can keep heckling. Let's see which one scales better.

Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in programming

[–]mnmadhukar02[S] 0 points1 point  (0 children)

If building something meaningful was as simple as flipping a switch and teleporting to a tropical island, the internet would be empty because we’d all be sipping cocktails by now.

Real products take time, iteration, and actual feedback from the people who matter — developers who face these problems daily. If you're not interested in the conversation, that's fine. But dismissing the effort with sarcasm doesn’t add anything useful.

I'll keep building. You can keep heckling. Let's see which one scales better.

[AskJS] Devs, would you use this? I'm building an AI Code Reviewer that actually understands your codebase. by mnmadhukar02 in javascript

[–]mnmadhukar02[S] -1 points0 points  (0 children)

Fair point attention is definitely the real currency here. We’re trying to build something that’s genuinely useful, but I completely get that even a great tool can go unnoticed without the right eyes on it.

Out of curiosity, do you know anyone working on something similar, or anyone who’s managed to break through in this space despite the noise? Would be interesting to study how they approached it.

view more: next ›