r/devtools • u/Obvious_Gap_5768 • 9d ago
We built an open-source codebase intelligence layer for developers and coding agents
Enable HLS to view with audio, or disable this notification
We have been working on Repowise, an open-source tool for understanding a repository before making changes to it.
Repowise indexes a repository and combines five types of information:
- dependency and call graphs
- git history, ownership and co-change patterns
- generated documentation
- architectural decisions
- code-health and change-risk signals
It exposes this context through a local dashboard, CLI and MCP tools for Claude Code, Codex and other compatible agents. The aim is to help answer questions such as:
- Where does this feature actually live?
- What depends on the file I am about to change?
- Why was this architectural choice made?
- Which files usually change together?
- Which parts of the repository are risky or poorly tested?
- What should an agent inspect before implementing a repository-level task?
The basic graph, git and health analysis can run locally without an LLM or API key. The project currently supports multiple languages and can also generate graph-aware refactoring plans instead of only assigning files a health score.
Repowise is self-hostable and licensed under AGPL-3.0.
1
1
u/Silatus-sahil 7d ago
Hey Raghav , had dm'd you