whatisgithub

What is reposcope?

whoknowsasaint/reposcope — explained in plain English

Analysis updated 2026-05-18

1TypeScriptAudience · developerComplexity · 3/5LicenseSetup · moderate

In one sentence

A tool that lets you ask plain-English questions about any GitHub repo's code and get answers with exact file paths and line numbers.

Mindmap

A visual breakdown will appear here once this repo is fully enriched.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Ask questions about an unfamiliar codebase and get answers pointing to exact files and lines.

USE CASE 2

Index a cloned repository locally and search it with natural language instead of grep.

USE CASE 3

Have a follow-up conversation about a codebase with context preserved across questions.

What is it built with?

TypeScriptPythonFastAPIChromaDBNext.js

How does it compare?

whoknowsasaint/reposcope0xkinno/neuralvault0xmayurrr/ai-contractauditor
Stars111
LanguageTypeScriptTypeScriptTypeScript
Setup difficultymoderatehardeasy
Complexity3/54/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires a Groq API key for the LLM and local storage for cloned repos and embeddings.

So what is it?

Reposcope is a tool that lets you ask plain-English questions about any GitHub repository's code and get back answers with exact file paths and line numbers. It uses a technique called RAG (Retrieval-Augmented Generation), which means it first indexes the codebase into a searchable form, then uses that index to retrieve relevant code snippets before generating an answer. The indexing step clones the repository and splits the code into chunks using AST-based (Abstract Syntax Tree) chunking via tree-sitter, which splits code at meaningful boundaries like functions, classes, and methods rather than arbitrary character counts. Those chunks are turned into vector embeddings, numerical representations that capture meaning, and stored locally in ChromaDB, a local vector database. When you ask a question, the most relevant chunks are retrieved and passed to an LLM (Groq running Llama 3.3 70B) to generate the answer. Conversation history is preserved across questions in a local SQLite database, so you can ask follow-up questions that reference earlier context. You can use it either through a command-line interface or through an optional web interface built with Next.js and Tailwind CSS. The backend is FastAPI, the CLI uses Click and Rich, and embeddings are generated using Jina AI's jina-embeddings-v3 model. Everything, cloned repos, embeddings, and conversation history, is stored locally in a folder in your home directory. The project is written in TypeScript for the frontend and Python for the backend, and is licensed MIT.

Copy-paste prompts

Prompt 1
Show me how to index a GitHub repo with Reposcope and ask my first question about it.
Prompt 2
Explain how Reposcope's AST-based chunking splits code differently from plain character-based chunking.
Prompt 3
Help me set up the optional Next.js web interface for Reposcope.
Prompt 4
Walk me through how Reposcope stores conversation history in SQLite for follow-up questions.

Frequently asked questions

What is reposcope?

A tool that lets you ask plain-English questions about any GitHub repo's code and get answers with exact file paths and line numbers.

What language is reposcope written in?

Mainly TypeScript. The stack also includes TypeScript, Python, FastAPI.

How hard is reposcope to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is reposcope for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.