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 context

show exact code snippets, references, and confidence signals in chat answers

detect architecture drift and endpoint changes over time

send alerts for meaningful changes and failed analysis runs

track workspace usage, plan limits, and operational health

What This Changes

Version 1 helped understand a repository.

Version 2 helps understand change.

That means RepoLens starts becoming useful in everyday engineering workflows, not just onboarding.

For example:

reviewing pull requests

tracking architecture changes across runs

seeing what modules and endpoints were affected

understanding branch differences faster

getting grounded answers in the exact context you care about

receiving alerts instead of checking manually

Product Direction

The RepoLens product story is becoming clearer:

Version 1: Know any repo fast.
Version 2: Know what changed and what matters.

That shift is the part I’m most excited about.

RepoLens is moving from static repository understanding
to ongoing engineering intelligence.

Live Platform
https://repolensai.com

Open Source Repository

The open-source analysis engine is available here:

https://github.com/mohosin2126/repolens-community

Version 2 LinkedIn Post
https://www.linkedin.com/posts/mohosin2126_opensource-ai-github-activity-7442612868300234752-HWkc?utm_source=share&utm_medium=member_desktop&rcm=ACoAADpg8RMBJaipaeKrpBc7xSoC8S90bR4HWpk

Why I Built Version 2

I wanted RepoLens to be useful not only when someone first opens a repository,
but also when a team is actively changing it.

Especially when:

reviewing pull requests

tracking risky changes

watching API and architecture evolution

keeping teams aligned as systems grow

Open Core

RepoLens continues to follow an open-core model.

The reusable analysis engine remains open source, while the hosted platform builds on top of it with collaboration, change intelligence, notifications, workspace controls, and premium product features.