Precision across the graph and Code Health, and a free Pro trial

The open-source release, 0.55.0, is about precision. The call graph, dead code, health and refactoring advice stop reporting what the evidence does not support, and Code Health gains one Fix first queue. On repowise.dev you can also try Pro free, and ChatGPT and Cursor can connect to the MCP server.

A more precise call graph

Call resolution follows each language. Receivers are typed through struct fields, locals and constructors in Go and Rust, super() follows the method resolution order in Python, and a parameter that shadows a name no longer resolves to the module-level symbol. Java, C# and C++ overloads each get their own symbol, so a call draws an edge to the overload it names.

Dead code is quieter for entry points and files a tool loads by name, and an unused export reaches full confidence only when an importer names it. Refactoring and performance advice that would not help is withheld.

On repowise.dev. A repository shows these results after its next index. Snapshots indexed before the upgrade keep their old results until then.

One Fix first queue

Below the score, Code Health now has Fix first: one ranked list built from the stored findings across defect, maintainability and performance. Open an item for its steps, a Verify block and the reason for its rank. A performance item points at the loop header line it changes. Code that does not ship (vendored, generated, docs examples, tooling, tests) stays out unless you tick Include tests. Suggested tests are ordered by measured coverage of the changed lines, when your CI uploads a coverage report, then by tests that name the changed symbol.

Free Pro trial

On repowise.dev.

A personal Pro checkout can start with a free trial. The trial needs a card, and the card is charged the day the trial ends unless you cancel first. The pricing page shows the length and the day it ends, and Billing shows the time left, with a reminder three days before the first charge. The trial starts with a small credit balance, and the first charge converts it to a normal Pro plan. It is one trial per person, offered to accounts that have not paid before.

While a trial is on offer, the home page invites private repos too: add one and checkout takes you on to the indexed repo.

Lens in Claude Code

Lens is the part of the Repowise plugin for Claude Code that you see. It runs on your machine against your local index. A band above the prompt tells you when the index is behind or something needs setting up, a review of the change appears after a turn that edits files, and /lens opens a pane with a per-turn Flow dashboard and a map of the repository lit by what Claude reads and edits. It needs Claude Code 2.1.287 or later and an indexed repo. See what Lens shows and how to install it.

Files health cannot analyse show as not analysed

Languages without a health dialect used to be stored at a perfect score, so every PHP file in a Laravel repository read as perfect. They now store no score and are left out of averages, hotspot health, band counts and trends. The code health map draws them grey and the file drawer says "Not analysed". A repository's next index stores the change.

Agents

• MCP results are compact JSON with a lean _meta.
• get_answer names the files to read at every confidence, and search_codebase spends its results on distinct files, with one path per row.
• get_context caps the symbol card, types first, and says how to ask for the rest.

Module pages from facts

Module pages are written from structured facts about the module: its parts, import edges, key files and public API. Mermaid diagrams are validated before a page is stored, and a cited file that does not exist is dropped. The overview opens with a tiered system map built from the repository's manifests.

On repowise.dev, a module page is rewritten this way when its code changes or the repository is new.

Also on repowise.dev

• ChatGPT and Cursor can connect to the MCP server over OAuth.
• A coverage report your CI uploads from a push to the default branch becomes the repository's coverage. Pull request and other-branch uploads do not change it.
• Doc drift findings are marked new or carried across index runs.
• The Refactoring board opens on what Fix first would take, with a Scope control for the full inventory.

Also in the open-source release

• repowise publish puts a local repository on repowise.dev.
• repowise dead-code and repowise health --refactoring-targets read the stored results.

Upgrading

pip install --upgrade repowise

After an upgrade, repowise update re-scores and re-parses an unchanged checkout and says so, with no model call. On repowise.dev, a repository shows the new scores and precision after its next index.