All activity
Md Mohosin Ali Shahstarted a discussion
What signal would help your team most when code is changing fast?
While building RepoLens, one thing became very clear to me: understanding a repository is one problem, but understanding what changed and what actually matters is a different one. That’s the direction behind RepoLens Version 2. I’m trying to learn which signals would be most valuable for real engineering teams when repositories are moving quickly. If you could get one of these automatically...
Md Mohosin Ali Shahleft a comment
One thing I’d really love feedback on: If you work in fast-moving repositories, which signal would be most useful to you first? PR summaries affected modules changed endpoints review hotspots branch-aware chat architecture drift alerts Curious which one feels most valuable in real engineering workflows.
RepoLensKnow what changed and what matters across your codebase
Md Mohosin Ali Shahleft a comment
I built RepoLens Version Two to solve the next problem after repository understanding: understanding change. Version One helped developers understand unfamiliar repositories faster through module maps, dependency graphs, API discovery, generated docs, grounded repo chat, and branch comparison. But understanding a repository once is not enough. Repositories keep changing. Pull requests introduce...
RepoLensKnow what changed and what matters across your codebase
RepoLens Version Two helps engineering teams understand what changed and what matters across repositories, branches, and pull requests. It analyzes PRs, detects affected modules and changed endpoints, highlights review hotspots, powers branch-aware chat with grounded code references, compares branches structurally, and sends alerts for important changes so teams can understand evolving codebases faster with more trust.
RepoLensKnow what changed and what matters across your codebase
Md Mohosin Ali Shahleft a comment
I built RepoLens Version One to solve a simple but frustrating problem: understanding an unfamiliar codebase takes too long. When developers open a new repository, they need more than a file tree. They need to understand the project structure, module relationships, dependency flow, API surface, architecture, documentation, and branch-level changes. RepoLens V1 is designed to make that process...
RepoLensUnderstand any codebase in minutes, not weeks
RepoLens Version One helps developers understand unfamiliar codebases faster. Paste a repo URL or connect GitHub, and RepoLens analyzes the project to generate module maps, dependency graphs, API endpoints, architecture summaries, onboarding docs, grounded repo chat, and branch comparison views. It stands out by turning raw repositories into structured, explorable knowledge with answers linked back to real source files so you can verify everything.
RepoLensUnderstand any codebase in minutes, not weeks
Stop wasting time wiring React, Next.js, Vue, Express, Prisma, and Mongoose together. Starter Structure CLI scaffolds production-ready apps from simple stack tokens like `react vite ts tailwind express prisma mysql`. Get the right folders, configs, and boilerplate instantly. Includes 30+ starters across 6 categories. TypeScript-first, zero config, one command, works with `npx`.
Starter Structure CLIScaffold 30+ full-stack apps from stack tokens instantly
Md Mohosin Ali Shahleft a comment
Hey Product Hunt! I built Starter Structure CLI because I was tired of spending the first 2 hours of every project doing the same thing: setting up folders, wiring frontend to backend, configuring Prisma/Mongoose, adding auth boilerplate, and connecting everything with Tailwind. The idea was simple what if I could just describe my stack and get a working project instantly? So I built a modular...
Starter Structure CLIScaffold 30+ full-stack apps from stack tokens instantly