I built a tool that turns any GitHub repo into an interactive architecture map

The problem We've all been there. You join a new team, clone the repo, and stare at 500+ files wondering: where do I even start? You open a service file. It imports from 3 other modules. Those modules import from 5 more. Twenty minutes later, you're 12 files deep and you've already forgotten where you started. I spent years doing this manually — drawing architecture diagrams on whiteboards that were outdated by the next sprint. So I built something to fix it. What is ReposLens? ReposLens takes a GitHub repository and generates an interactive dependency graph of its architecture. Services, databases, queues, gateways — all mapped as nodes and edges you can click, drag, and explore. But it goes beyond visualization: 🔍 8 Architecture Detection Rules The engine analyzes your graph and detects real problems: Circular dependencies — A depends on B, B depends on A Layer violations — your database layer depending on your frontend Diamond dependencie — two modules sharing a transitive dependenc