RepoLens
Know what changed and what matters across your codebase
126 followers
Know what changed and what matters across your codebase
126 followers
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.
This is the 2nd launch from RepoLens. View more
RepoLens
Launched this week
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.
Free
Launch Team / Built With
RepoLens
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.
How is this different from just using ChatGPT on a repository or asking GitHub Copilot questions?
RepoLens
@hira365 Great question.
RepoLens is built around structured repository and change analysis, not just general code Q and A. Instead of only answering questions like ChatGPT or Copilot, it maps pull request changes, detects affected modules and endpoints, highlights review hotspots, and keeps the insight grounded in actual repository and diff context.
The focus is helping teams understand what changed and what matters, not just chat with the codebase.
Crossnode
We need this in my team!!
RepoLens
@rania_rimali Thank you. I really appreciate that.
I would be interested to know which capability would be most useful for your team in practice PR summaries, review hotspots, changed endpoints, or branch aware chat.