repowise

Repowise provides a single, continuously updated index for a codebase that includes its structure, Git history, test coverage, and recorded architectural decisions. The index refreshes on every commit so any consumer sees the most recent state. The tool is available as an open‑source command‑line interface that you can run locally, and a hosted version that adds a web dashboard and CI integration.

For developers who need to understand the ripple effect of a change, Repowise pulls the list of callers for any target function or file, shows the dependent files downstream, and lists the tests that hit those callers. In practice you run a command like `repowise mcp get_context <symbol>`, and the output lists the exact lines, the callers, and the tests to run first. When a pull request is created, the Repowise bot posts a single comment that enumerates the callers, the files that typically move together, and the tests that should be executed before merge. Teams can then see potential blast‑radius problems before the code lands.

Every merge creates a Change Record that contains the owners, the tests that ran, and the decisions that the change traversed. During CI the `repowise check` command can enforce policy checks, such as requiring an owner review for changes that cross a recorded decision. This keeps the evidence behind every merge and forces reviewers to look at the context that a change touches.

File‑level health scoring is another core feature. Each file receives a defect‑risk, maintainability, and performance score. Hotspots and dead code are highlighted with a name‑and‑says‑cure fix. For example, a file containing an API wrapper may get a defect risk of 6.4 and a recommended refactor to split long functions. The dashboard shows these scores so that the most risky files can be prioritized for refactoring or additional tests. Repowise claims a 2.3× increase in defect detection compared with a baseline, and a 31.6 % reduction in AI output tokens when integrated into a coding workflow, according to its own benchmarks.

Repowise works best for teams that already use pull‑request workflows and want a single source of truth for code health and decision history.