AI-powered GitHub repository analysis — just add m before any github.com URL

Website · Quick Start · Features · AI Providers

Pro tip: Turn any GitHub URL into a RepoLens analysis by adding m before github.com. For example: github.com/facebook/react → mgithub.com/VrianCao/Uptimer

• Repository Overview — Instant project summary, tech stack detection, and interactive file tree visualization
• Code Browser — Syntax-highlighted source viewer powered by Shiki, with file outline and breadcrumb navigation
• Issues Scanner — Automated code quality analysis that detects security vulnerabilities, performance problems, and best practice violations
• Diagrams — Auto-generated architecture diagrams using Mermaid.js — dependency graphs, component relationships, and more
• Documentation Generator — AI-powered docs generation with 6 presets, including Architecture, Setup, API Reference, File Explanation, Onboarding, and Custom
• AI Chat — Ask questions about a selected codebase with 15 progressively available analysis and skill tools
• Pull Requests — Browse pull requests, changed files, and diffs without requiring indexed source content
• Code Tours — Build deterministic local walkthroughs from repository paths and symbols; use Chat for AI-authored walkthroughs
• Compare — Side-by-side repository comparison with similarity/clone detection scoring to evaluate alternatives
• Git Insights — Coding hours estimation, activity punchcard, and per-author contribution charts derived from commit history

1. Navigate to mgithub.com/owner/repo (or paste any GitHub URL on the homepage)
2. RepoLens resolves the Git tree adaptively and reports when GitHub returns a truncated or partial result
3. Supported content is loaded through a ZIP or per-file fallback; very large repositories load content on demand
4. Complete, failure-free indexes can be cached in IndexedDB for repeat visits; the coverage banner reports what was discovered and loaded

RepoLens supports 4 AI providers. You configure API keys directly in the app — no environment variables needed.

Add a GitHub Personal Access Token (PAT) to access private repositories and raise GitHub's account-level API limit from 60 to 5,000 requests/hour. RepoLens applies separate endpoint-specific proxy limits. The PAT is stored in your browser. RepoLens may send it through its server for validation, ZIP downloads, and some GitHub requests; other supported requests may go directly from the browser to GitHub.

1. Create a fine-grained PAT on GitHub.
2. Grant Contents: Read-only and Metadata: Read-only permissions (select only the repositories you need, or choose All repositories).
3. In RepoLens, click the gear icon (Settings) → GitHub tab → paste your token → Test Connection.

• The token is stored in your browser's localStorage — same as AI API keys.
• Depending on the operation, authenticated GitHub traffic may go directly from the browser to GitHub or through RepoLens server routes.
• OAuth sign-in continues to work through server-side proxy routes. GitHub OAuth Apps require the broad repo scope for private code because they do not offer a read-only private-code scope; use a fine-grained PAT when you need repository-specific read-only access.

git clone https://github.com/zebbern/repolens.git
cd repolens/workproject
pnpm install
pnpm dev

Open http://localhost:3000, click the gear icon (Settings), and enter your API key(s).

AI API keys are stored in your browser. When you use an AI feature, the selected key, your prompt, selected repository context, and local tool results are sent through the RepoLens server to the selected provider.

AI keys are configured in the UI — no environment variables required for basic usage.

1. Fork the repo and create a branch.
2. Make your changes.
3. Run pnpm test to verify.
4. Open a pull request.