👁️ repo-lens
Your repository's third eye.
Forget manually digging through git logs and grepping for context. repo-lens combines deep Git history analysis with advanced AI reasoning to give you instant clarity on your codebase. Whether you're hunting for the origin of a bug or summarizing years of commits, repo-lens sees what you might miss.
Powered by smolagents for iterative reasoning and LiteLLM for universal model support (OpenAI, Anthropic, Ollama, Qwen, and more).
🛠️ Prerequisites
Before you start peering into your repos, ensure you have:
- Python 3.11 or higher.
- Git installed and available in your PATH.
- Access to an LLM provider:
- Cloud: OpenAI, Anthropic, etc. (API Key required).
- Local: LM Studio, Ollama, or vLLM (OpenAI-compatible server running).
🚀 Installation
Install repo-lens directly from this repository for the latest features:
# Using uv (recommended)
uv tool install repo-lens
# Using pip
pip install repo-lens
To build from source:
git clone https://github.com/satishjasthi/repo-lens.git
cd repo-lens
uv sync
⚙️ Getting Started
repo-lens is configured via environment variables or a .env file in your current directory.
Create a .env file:
# LLM Configuration
REPO_LENS_PROVIDER=openai # openai, anthropic, ollama, etc.
REPO_LENS_MODEL=openai/gpt-oss-20b # Your model identifier
REPO_LENS_API_BASE=http://localhost:1234/v1 # Base URL for local SLMs
REPO_LENS_API_KEY=sk-... # Your API key (if needed)
# Repo Settings
REPO_LENS_REPO=/path/to/your/repo # Optional defaults to current dir
REPO_LENS_TIMEOUT=60 # HTTP timeout
🤖 Running the Agent
The agent command (Iterative Reasoning)
The agent command is the powerhouse of repo-lens. It doesn't just guess; it reasons. It plans Git commands, observes the results, and refines its search until it finds the answer.
repo-lens agent "Who added the bedrock support and what files did they change?"
The ask command (Quick Context)
For simple questions based on the recent history and current state:
repo-lens ask "Summarize the changes in the last 5 commits"
Thin Git Wrappers
repo-lens also includes thin wrappers for common Git tasks:
repo-lens git status
repo-lens git log --limit 5
repo-lens shell "ls -la"
📦 PyPI Publishing
Built with uv, repo-lens is ready for the world. To publish your own version:
- Update
pyproject.tomlwith your details. - Build the package:
uv build - Publish to PyPI:
uv publish
Author: Satish Jasthi
License: MIT
Metadata
Release files for repo-lens 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| repo_lens-0.1.3.tar.gz | 13.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| repo_lens-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.9 kB
Release files / repo_lens-0.1.3.tar.gz
| Download URL | repo_lens-0.1.3.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16a8585c665fd9e30531e924ec38ec654481d343edc4a36cfb42e1a21694eb6c
|
|
BLAKE2b-256 checksum How to use checksums |
6dba2baec5c815a0e5005e0c48dd72c41335a9fb6dc49dd5c44edfb4e126dab9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 14, 2026.
Transparency logRelease files / repo_lens-0.1.3-py3-none-any.whl
| Download URL | repo_lens-0.1.3-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
61b745b395b9947c7a74fe70e5729c98b86e17a7d20d7d776530436a9a1f4970
|
|
BLAKE2b-256 checksum How to use checksums |
bcb1e62ab0678d0d261b164f77942e97b4225ae23704a57bf038328831f39450
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 14, 2026.
Transparency log