I am working on devlens.io , It automatically maps your codebase dependencies and drops precise structural insights directly into your GitHub PRs. No hallucinations, just hard context.
It is an open-source project and I will introduce soon its mcp/cli counterpart so that graphical context and sumaries can be given to LLMs/Agents directly through the mcp integration.
Maybe, in your experience, but I have tried both claude and codex and the code quality that claude produces is still superior in my experience, maybe its because of the nature of app I am building
Currently Working on https://devlens.io which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review.
The open source version is live at https://github.com/devlensio/devlensOSS
You can star the repo if you like the project. I am still working on cloud version which will have lots of features.
Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file/function where it will affect my Codebase which is specially useful for PR review.
Also the main MOAT of Devlens is not the visualizer but the blast radius feature. Which essentially tells you if I change this file/function where it will affect my Codebase which is specially useful for PR review.
Currently Working on https://devlens.io which is an Open source Intelligent Codebase Visualizer for javascript, Reactjs, nextjs and nodejs for easy onboarding and easy PR review.
While working with larger React / Next.js codebases, I noticed a lot of PR review time goes into understanding the impact of a change rather than the change itself.
Things like:
what depends on this? what else could this affect? how far does this propagate?
usually require a lot of manual tracing across files and components.
So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.
Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.
While working with larger React / Next.js codebases, I noticed a lot of PR review time goes into understanding the impact of a change rather than the change itself.
Things like:
what depends on this?
what else could this affect?
how far does this propagate?
usually require a lot of manual tracing across files and components.
So I started building Devlens — a tool that visualizes the codebase as a graph and shows the “blast radius” of components/changes to help with PR reviews, onboarding, and understanding unfamiliar parts of a system.
Curious whether teams here would actually find something like this useful in real workflows, or if this mostly gets solved through experience and familiarity with the codebase over time.
It visualizes React / Next.js codebases as an interactive graph so you can understand how features and components connect without manually tracing files.
Main focus right now is helping with:
PR reviews (understanding blast radius / impact of changes)
onboarding to large codebases
understanding unfamiliar parts of a system faster
Also experimenting with summaries + security analysis directly on components.
Still early, but it’s been pretty useful for me so far.
Getting too much dependent on LLMs will eventually rust out my brain. I started notificing using tools like claude code and cursor, is ontroducing blackbox around architecture around my own Codebase. And I literally hated it when someone dont understand their own codebase
If you are building something which can be vibe-coded easily then it ofc people will create it. You can copyright a product but you can't copyright an Idea.
Selling things online was an idea by Amazon, now everyone sells online.
If you really want people not to copy your idea then make something which cannot be easily vibe-coded or copied easily i.e. which require serious skills.