RepoLens

AI-native repo understanding workspace

Built for the three launch prompts in the spec

Turn confusing codebases intoevidence-backed product understanding.

RepoLens analyzes a repository, builds diagrams and explainers, surfaces risks and evidence, and gives your team a collaborative board instead of another disposable AI answer.

Launch RepoLens Explore the product

Explain this feature for a PM.

What changed in this PR and what should QA test?

Onboard me to this code area.

Board workspace

Evidence cards, explainers, diagrams, and chat all grounded in the same repository state.

Live board

CanvasPM view

Checkout Flow

Value proposition, user journey, and the routes that power payments.

Payment Architecture

Mermaid diagram from the repo with confidence metadata.

Evidence Panel

`checkoutService.ts:34-78` · `POST /api/pay` · `STRIPE_KEY`

Find the billing retry logic

Semantic search jumps straight to the matching explainer, brief, or diagram on the canvas.

Trust

Explicit evidenceInferred sectionsPersisted chat

GitHub sync

Encrypted board credentials + webhook-driven re-analysis

Board-gated access and encrypted repo credentials

Explainers, change briefs, and canvas artifacts persisted in Supabase

Searchable understanding layer over your repository

Why teams buy

RepoLens turns repo analysis into a product surface your company can actually reuse.

It is not just a prompt box. It is a system for durable understanding: structured outputs, collaborative review, evidence controls, and saved boards that live beyond one chat session.

Evidence-backed understanding

Every explainer, brief, and diagram stays anchored to code evidence, confidence signals, and the files that matter.

Built for product and engineering

Switch between PM, Engineer, and Deep Dive views without rerunning the analysis or losing context.

A collaborative canvas, not a chat log

Turn repo analysis into durable boards your team can review, annotate, search, and refine together.

Core workflows

The three launch moments already map cleanly to the product.

The landing page stays aligned to the spec: feature understanding, change comprehension, and fast onboarding.

Feature explainers for PMs

See why a system exists, what it does, and which code proves it.

Change briefs for releases

Turn diffs into impact, rollout risk, and QA guidance your team can trust.

Onboarding for new teammates

Map flows, services, and product concepts without reading the whole repo alone.

What the product already does

The current build now covers the core intelligence loop and board workflows.

Stage 1 repo graphing with structural, application, and product signals

Semantic artifact search across explainers, briefs, and diagrams

Board-level GitHub credentials with encrypted storage and webhook sync

Evidence panels, confidence levels, annotations, and chat history

Canvas persistence for positions plus editable content inspector

Explainer and change-brief artifacts persisted for reuse and export

Why this matters for go-to-market

The product can now be positioned as a trusted understanding layer for product, QA, and engineering.

RepoLens is strongest when it proves something with evidence, turns that into a reusable artifact, and lets a team refine it together on a board.

That makes the homepage narrative simple: analyze repos, explain intent, review change impact, and keep the output alive as collaboration happens.

Ideal first user

Product or engineering lead dropped into a complex codebase.

Launch-ready narrative

Give your team a faster path from repository to shared understanding.

Start with a repo, generate evidence-backed explainers and change briefs, then turn them into a board your team can review and trust.

Try RepoLens See the workflow

Turn confusing codebases intoevidence-backed product understanding.

RepoLens analyzes a repository, builds diagrams and explainers, surfaces risks and evidence, and gives your team a collaborative board instead of another disposable AI answer.

Explain this feature for a PM.

What changed in this PR and what should QA test?

Onboard me to this code area.