Repowise / code-review-graph
Repowise vs code-review-graph: the decision is not a checklist.
Choose between a review-oriented graph and wiki, or a broader intelligence layer used across review, planning, onboarding, and maintenance.
code-review-graph produced the most precise retrieval set in the Repowise benchmark, with lower coverage. It is a credible focused option when compact review context matters more than the wider evidence surface.
- Category
- Open-source graph and wiki for code review
- Reading rule
- Different product philosophies are explained before individual capabilities are compared.
01 / Category framing
What each product is built to do.
- Repowise
- A persistent codebase-intelligence layer that combines structure, git history, decisions, code health, generated documentation, and MCP retrieval for both people and coding agents.
- code-review-graph
- A local graph and generated wiki designed to provide codebase context for pull-request review agents.
02 / Overlap and difference
Where the workflows meet, and where they diverge.
Genuine overlap
- Both build a code graph and generated repository knowledge for agent consumption.
- Both can support context-aware code review.
- Starting point
- code-review-graph focuses its graph and wiki on review. Repowise exposes additional history, health, decisions, risk, and general retrieval workflows.
- Operating model
- Both are open-source local systems. Setup constraints and agent tool adoption are documented in the benchmark, not hidden.
- Evidence boundary
- The benchmark records high precision and lower coverage, plus different adoption across Codex and Claude. Those observations are harness-specific, not a verdict on universal agent behavior.
03 / Concise comparison
Compare the operating questions.
Text carries every distinction. Color and icons are not required to understand this table.
Scroll sideways to read both products and the caveat column.
| Buying question | Repowise | code-review-graph | Boundary |
|---|---|---|---|
| What is the primary job? | A persistent codebase-intelligence layer that combines structure, git history, decisions, code health, generated documentation, and MCP retrieval for both people and coding agents. | A local graph and generated wiki designed to provide codebase context for pull-request review agents. | These categories overlap, but they are not interchangeable. |
| How does work begin? | Index a repository, then inspect or query the persistent evidence model. | code-review-graph focuses its graph and wiki on review. Repowise exposes additional history, health, decisions, risk, and general retrieval workflows. | Evaluate this against the workflow your team already owns. |
| What can a human inspect? | Generated documentation, architecture, dependencies, history, decisions, code health, and risk views. | The code-review-graph surfaces described in its linked primary documentation. | The page avoids inferring capabilities that the source does not document. |
| What can an agent use? | MCP tools for answers, search, context, symbols, rationale, risk, health, and repository overview. | The agent or integration surface documented by code-review-graph. | Tool count alone is not treated as capability or outcome quality. |
| Where can it run? | Hosted, or self-hosted from the open-source distribution. | Both are open-source local systems. Setup constraints and agent tool adoption are documented in the benchmark, not hidden. | Confirm current plans, deployment terms, and data handling with the vendor. |
04 / Repowise evidence
Inspect the product, not a scorecard.
The links below open current output for the named Repowise repository. Measured claims, when relevant to this decision, come directly from the benchmark fact registry and keep their sample and caveat attached.
05 / Fit
Choose Repowise when...
- You need broader retrieval coverage with file, history, health, and decision evidence.
- You want the index to serve human browsing and workflows beyond pull-request review.
Honest trade-off
Choose code-review-graph when...
- You want a focused local graph and wiki for review-oriented agents.
- High retrieval precision matters more than finding a larger share of relevant files.
06 / Verification notes
What this brief does not claim.
- Measured results apply only to the named corpus, commit, harness, sample, and setup in the linked benchmark.
- Competitor capabilities, packaging, deployment terms, and prices can change after the verification date.
- A product-category comparison is not a security, compliance, procurement, or legal assessment.
- Repowise evidence links show current product output; they are demonstrations, not proof that every repository will produce the same findings.
External facts checked August 27, 2026
- code-review-graphPrimary open-source repository for graph, wiki, MCP tools, and setup.Inspect code-review-graph source
- Repowise BenchThe benchmark records high precision and lower coverage, plus different adoption across Codex and Claude. Those observations are harness-specific, not a verdict on universal agent behavior.Inspect benchmark methods and raw results
Common questions
Everything people ask before they try it.
Is Repowise a direct replacement for code-review-graph?
Not automatically. code-review-graph is primarily open-source graph and wiki for code review, while Repowise is a broader repository-intelligence layer. The right choice depends on the job described in the fit section.
When should a team choose code-review-graph?
You want a focused local graph and wiki for review-oriented agents. High retrieval precision matters more than finding a larger share of relevant files.
When should a team choose Repowise?
You need broader retrieval coverage with file, history, health, and decision evidence. You want the index to serve human browsing and workflows beyond pull-request review.
Are the claims on this page benchmarked?
Only the explicitly labeled benchmark evidence is measured. The benchmark records high precision and lower coverage, plus different adoption across Codex and Claude. Those observations are harness-specific, not a verdict on universal agent behavior.
Start with a real repository.
Browse Repowise output before you make the product decision. No account is required for public repositories.