GREPO — Find Your Way Through the Code

A repository is easy to clone and hard to understand. Before making a useful change, a developer must discover where behavior lives, how modules connect, what can be reused, and what might break. That knowledge is scattered across file trees, searches, documentation, and teammates' memories. GREPO brings it into one workspace: a connected path from repository structure to source evidence to a reviewable next step. Import a public GitHub repository or ZIP to create a read-only snapshot. Start with the overview, search the file tree, explore an interactive repository map, and open the corresponding source without losing your place. Shared selection and source ranges keep the map, files, and findings connected. The dependency explorer traces supported static imports and function calls, attaches source evidence, and explains unresolved relationships. Reusable functions, duplicate patterns, and potentially unused code become concrete starting points for investigation. File and folder summaries surface inventory and syntax facts. Coverage information helps developers judge what the analysis can establish. The recorded workflow also demonstrates optional AI assistance. Ask a repository question, inspect the cited excerpts, and follow them back to source. Describe an improvement to generate a change proposal with affected files, suggested checks, and open questions. Create an onboarding guide, repository overview, or developer reference, then edit and export the Markdown. These outputs remain reviewable drafts; the imported code stays untouched. GREPO is designed for developers joining a codebase, maintainers investigating unfamiliar modules, and contributors preparing a change. Its value comes from keeping exploration, explanation, and planning close to the evidence. Instead of rebuilding context in separate tools, users can carry what they discover directly into their next question or decision. Underneath the interface, snapshot-scoped identifiers, source hashes, bounded reads, and explicit unresolved states provide a traceable foundation. Core exploration runs locally without executing imported code. Optional Groq-powered AI works through the backend with selected source excerpts. React and TypeScript power the interface; Python, FastAPI, Tree-sitter, and Archify support analysis and visualization. IBM Bob was a central development tool for the team's implementation and corrective engineering. GREPO helps developers find their bearings, inspect the evidence, and approach the next change with a clearer understanding of the code.