RepoLens Version 2 - Know what changed and what matters

RepoLens Version 1 was about understanding a repository quickly. It helped answer: What is in this repository? How is the codebase structured? Where do I start? But after building and using it more, I realized something important: understanding a codebase once is not enough. Repositories keep changing. Pull requests introduce risk. APIs evolve. Architecture drifts. And teams need better visibility into what changed, what was affected, and what actually matters. So I built RepoLens Version 2. RepoLens is no longer just a repository analysis dashboard. It is becoming a change intelligence platform for engineering teams. What RepoLens V2 Adds RepoLens can now: analyze pull requests and generate engineering summaries show affected modules, changed endpoints, and likely review hotspots run incremental analysis instead of reprocessing the whole repository every time sync automatically from GitHub push, PR, and merge events answer chat questions in repository, branch, PR, and branch-compare c