Meet CodeSloth — because Ctrl + Click is not a software architecture strategy.
Ever opened an open-source repo to make a tiny contribution and ended up questioning your career choices? Yeah, same.
💀 Problem Statement
Unfamiliar codebases are a maze of files, dependencies, APIs, and databases. Understanding how everything connects can take longer than the actual contribution.
🩹 Current Workaround
Open 37 tabs, chase imports, search for API routes, and pray the original developer left a comment. Spoiler: they didn't.
💡 Proposed Solution — CodeSloth
A local-first codebase explorer that turns GitHub repositories into:
- 🌳 Project Tree — Navigate the codebase without archaeological equipment.
- 🕸️ Dependency Graph — See which files depend on what.
- 🏗️ Architecture Flow — Visualize frontend → APIs → backend → databases.
- 🤖 Ask CodeSloth — Get AI-assisted code explanations using local Ollama models.
**💻 Source Code - https://github.com/praniket01/Codesloth
Demo
🎬 Live Demo: https://www.youtube.com/watch?v=cesLtzG88_s
Live Website: https://frontend-kappa-two-86.vercel.app/
⚙️ Working Model
Paste a public GitHub repository URL → CodeSloth indexes the codebase → explore its structure and connections → ask questions about the code using local AI.
Stack: Next.js · React Flow · FastAPI · SQLite · Ollama
🎯 The Mission
Make open-source contributions less intimidating by reducing the time spent understanding unfamiliar code and increasing the time spent building, fixing, and contributing.
The goal? Less spelunking. Fewer tabs. Faster pull requests.
Because life's too short to reverse-engineer an entire codebase just to fix one bug.
👉 Explore the demo, inspect the architecture, and let the sloth do the digging.
Top comments (0)