gitlore

Clarity through code anatomy

Speak fluent repository.

Drop any GitHub repo and watch gitlore summarize every file, function, and dependency — like a loyal teammate who already read the entire codebase before you arrived.

gitlore · cockpit

▼src/

▼components/

·auth/

·layout/

·ui/

·sections/

▶api/

▶context/

AI Summary — AuthButton.tsx

Client-side auth control. Renders a loading skeleton, then either a user avatar dropdown with sign-out, or a sign-in button — driven entirely by NextAuth session state.

File-tree AST

Call graphs

RAG Q&A

60-second scan

See it in action

What you get in 60 seconds

gitlore parses your entire repository and produces three artefacts immediately — explore any of them from the Cockpit Dashboard.

File map

src/api/analyze/route.ts

src/context/RepoContext.tsx

src/lib/gemini_adapter.ts

src/components/chat/

src/middleware.ts

+ 47 more files indexed

AI summary

src/api/analyze/route.ts

POST endpoint that validates the incoming repository URL or ZIP payload, enforces per-user rate and daily quotas via checkQuota(), then streams Gemini-generated analysis chunks back to the client using a TransformStream.

Exports

POST — analyze handler

GET — quota status

Chat with repo

Where is rate-limiting enforced?

In src/api/analyze/route.ts via the checkQuota() helper — 10 req/60 s per user, 100 req/day.

Which files own the streaming logic?

gemini_adapter.ts emits chunks; the route handler pipes them through a TransformStream to the client.

Ask anything about your codebase…

Integrates with

GHGitHub

VSCVS Code

GEMGoogle Gemini

PGPostgreSQL

50Ktokens/day

Context window per analysis

RAGpowered

Semantic search over your repo

100%server-side

Nothing stored client-side

The real cost of unfamiliarity

Know the feeling?

Every engineer has been dropped into an unfamiliar codebase. The first week is expensive — and not just for you.

Zero docs, 400 files

The README has two lines. The previous engineer is gone. You have a sprint starting Monday.

Ask the team? They're underwater.

Everyone is shipping. You can ask one question before you become the person who asks too many questions.

Read every file? There's a deadline.

A complete read-through of a mid-sized repo takes days. Your ticket is due in hours.

gitlore is the senior engineer who already read everything — available on demand.

Built for

Which one are you?

New to the team

Onboard in hours, not weeks

Drop the repo URL on day one. gitlore gives you a mental model of the entire codebase before your first standup — file purposes, entry points, key dependencies.

Analyze your new codebase →

OSS contributor

Contribute without the archaeology

Found a bug in an unfamiliar project? Ask gitlore where the relevant code lives, how it's connected, and what tests exist before you touch a single file.

Try it on any public repo →

Code reviewer

Review PRs with full context

Understand the intent behind every changed file. gitlore maps call graphs and module relationships so you review changes, not just diffs.

See the VS Code extension →

Three surfaces, one codebase

Three ways to understand any repo

Your repository, fully mapped

The Cockpit Dashboard presents every file with an AI-generated summary alongside its module graph. Navigate the codebase like you wrote it. Filter by directory, search by intent, not filename.

Try it yourself

Cockpit · file-map

FileSummary

route.tsPOST endpoint, streaming Gemini analysis

RepoContext.tsxGlobal repo state via React Context

gemini_adapter.tsStreams Gemini 2.5 Flash responses

AuthButton.tsxSession-aware auth toggle

How it works

Three steps, zero friction

No local setup. No config. Paste a URL and you're in.

Drop a URL or ZIP

Paste any public GitHub URL or upload a repository ZIP. gitlore accepts both — no installation, no config files, no CLI.

github.com/owner/repo or repo.zip

Watch it parse and embed

gitlore clones, walks every file, builds ASTs, extracts exports and call graphs, then embeds everything into a searchable vector store. Takes about 60 seconds.

Clone → Parse → Embed → Index

Ask, explore, and understand

Open the Cockpit Dashboard for the full file map, use OmniChat to ask precise questions, or generate architecture diagrams for any module.

Dashboard · Chat · Diagrams

VS Code Extension

Review PRs without
leaving your editor

The gitlore VS Code extension brings repository intelligence directly into your editor. Get AI summaries, ask questions about the code you're reading, and review PRs with full architectural context.

Inline file summaries in the Explorer sidebar
Ask questions about the file you have open
PR review mode — understand any diff in context
Zero login required for public repos

Install from VS Code Marketplace

route.ts·EXPLORER

PR #47

1export async function POST(req: Request) {

2const quota = await checkQuota(userId);

3if (!quota.ok) return new Response(...);

4const stream = await analyzeRepo(url);

gitlore · line 3

Early-return guard. If the user has exceeded their daily or rate-limit quota (checked via checkQuota()), returns a 429 before any Gemini call is made — keeping costs bounded.

Pricing

Free to try. Really.

No wizard. No trial expiry countdown. Sign in with GitHub and start analyzing immediately — here is exactly what you get:

50,000 tokens per dayEnough for a full medium-sized repo
100 analysis requests per dayRate-limited to 10 per 60 seconds
RAG-powered Q&AAsk anything, get precise answers
Architecture diagramsMermaid.js rendered in-browser
Full file-map with AI summariesEvery file, parsed and explained
VS Code extension accessSame token budget, no separate account

Start for free — no card needed

Privacy-first by default

Your code never leaves the analysis pipeline

No credit card required
GitHub OAuth only — no password stored
Tokens never logged or shared
Repos not persisted after session

Usage resets daily at midnight UTC. Token counts reflect the Google Gemini 2.5 Flash tokenizer. High-usage plans coming soon.

Ready when you are

Your next repo is one URL away

Drop any GitHub repository below. No setup, no configuration — just a URL and 60 seconds.