repowise-dev/repowise

Repowise indexes your code, call graph, git history, tests, docs and design
decisions once, on your machine. Then you and your coding agent ask it things:
what calls this, what breaks if I change it, what is dead, what to fix first, why it was built this way,
and what evidence stands behind each change that landed.
Free for one developer on a laptop. Built to run across a company's repositories.
−31.6% less agent output · p<0.0001
2.3× defects found vs CodeScene · p=0.003
15M lines of code indexed once on one laptop · then incremental on every commit
Graph, risk, health, tests and dead code make zero LLM calls · same diff, same answer ·
runs inside your network · scoped tokens for REST and MCP · change policy in CI with SARIF ·
free, AGPL-3.0 or commercial
Hosted ·
Foresight ·
What it does ·
Quickstart ·
Agents ·
Changes ·
Code health ·
Workspaces ·
Evidence ·
Enterprise ·
Docs
---
Repowise is an ambitious project. We want every engineer, and every agent working
beside them, to understand a codebase the way the person who has maintained it for
five years does: what calls what, what tends to break, what nobody uses anymore, and
why it was built this way. Cutting tokens was never the goal. It happens anyway,
because an agent that can ask the index stops searching, opening and re-reading
files to find out. Measured against the other context tools on the same agent
tasks, it is also the largest saving.
The same engine serves a developer who wants their agent to stop rediscovering the
code and a platform team that has to show what changed, who owns it and which tests
reached it. Every engine capability is in the free, open-source version. The
commercial layer adds organisation-wide operation on top.
Hosted, and Foresight
Everything in this README runs free on your own machine. repowise.dev
runs it for you, private repos included, and is where **Foresight** arrives first:
models trained on years of real commits and fixes that rank the files a fix will
touch, name what a change forgot, and explain every answer, with no LLM.
What Foresight does →
---
Set it up in one line
Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste:
The agent installs Repowise, indexes the repo with no API key, wires itself to the
index, and asks you before anything costs money. Prefer to do it yourself:
init wires Claude Code automatically. Then ask your agent *"Use Repowise
get_overview to summarize this repository"* or *"What breaks if I change
src/auth.py?"*
Full setup, every agent, optional model-written docs →
---
What it does
One index, three ways to use it. Find the question you came with; each one links to
the page that answers it.
Understand the code
| You ask | Repowise gives you |
|---|---|
| *How does checkout work in this repo?* | A cited answer built from the call graph and the generated docs, in one call. Search and answers |
| *What calls this function, and what does it call?* | A call graph across 27 parsed languages, every edge stamped with how it was resolved and how far to trust it, plus traced execution flows from each entry point. The graph |
| *Can I get docs for this codebase?* | A wiki for every module and file, rendered from the code's structure with no key, or written by a model when you choose. It updates incrementally after each commit. Docs |
| *Which of our docs are wrong?* | Markdown checked against the tree: every reference to a file or symbol the code no longer has, with the line to edit. Doc drift |
| *Why is it built this way?* | Decisions mined from ADRs, # WHY: comments, commit and PR history and your agent sessions, each tied to the code it governs and flagged when it goes stale. Decisions |
| *Who knows this code?* | Owners, bus factor, knowledge-loss risk when the main author goes quiet, and suggested reviewers. Ownership |
| *Can I see the architecture?* | An explorable dependency map, C4 views, and a Structurizr export, no model involved. Dashboard |
Change it safely
| You ask | Repowise gives you |
|---|---|
| *What breaks if I change this?* | Symbol-level blast radius: the callers of what you changed, the files that historically change with it but are missing from your diff, and the tests that reach it. Change risk |
| *How risky is this PR?* | Where the change ranks against your repository's own recent commits, with the reasons, as a directive your agent can act on. Change risk |
| *Which tests should run?* | The tests a diff actually exercises, from a coverage report if you have one and from the call graph if you do not. Test intelligence |