Plans an agent can apply, ranked by what they save

The open-source release, 0.56.0, turns refactoring advice into plans an agent can apply as written and ranks Fix first by what a change removes. On repowise.dev you can now connect GitLab projects, public repositories are ranked on leaderboards, and the PR bot answers in one comment.

Refactoring plans you can apply as written

A function too large for one helper gets a staged Extract Method plan. The function keeps its setup and calls the helpers in order, each stage at most CCN 10 and 60 lines, and every stage is anchored by the text of its first and last line. Plans over 5 stages arrive in batches with the tests to run between them.

Plan detail writes out each helper's header and the call that replaces the span, in the file's language (Python, TypeScript, JavaScript, Go, Java, Rust, C and C++), and quotes up to 5 nearest tests as runnable selectors. A plan also says which accepted decision governs its file and whether other code imports what it moves. Copy the agent prompt from an open plan to hand it on. Applied from the plan text alone on 15 of the top 30 "Break up X" items across three repositories, every resulting CCN matched the estimate.

C# plans are new, and C plans use the C++ dialect.

On repowise.dev. A repository shows the new plans on its Refactoring board after its next index.

Fix first ranks by complexity removed times reach

Worth is the complexity a fix removes, scaled by how many files import the file it lives in, and Do next and Fix first lead with the same item. On a Python agent repository a CCN 963 function rises from #25 to #1. The performance queue leads with loops that grow with the data, and a finding whose loop size is unmeasured never leads. Each finding stores its queue verdict at index time, so every view reports the same counts.

Code Health pages tell all-clear apart from not yet run, filtered out and error, and dead code reads as one figure and one list.

GitLab projects

On repowise.dev.

Connect GitLab.com under Settings, Git hosts, and add projects from any group or nested subgroup. repowise indexes each project, and its pages live at /repo/gitlab.com/group/project. With auto-sync on, a push to the default branch starts a new index when you are a Maintainer; otherwise repowise checks every 30 minutes. The PR bot reviews GitHub pull requests only.

Rankings for public repositories

On repowise.dev.

The leaderboard ranks public repositories with at least 500 stars and 100 files by code health, with a board for each of 13 languages and 6 groups such as coding agents and Python web frameworks. A ranked repository's page shows its place on each board, and its README badge shows the rank. Maintainers can claim their repository's page to get the badge snippets.

One comment on every pull request

On repowise.dev.

The PR bot folds its checks into one sticky comment with clearer health and AI review lines, and posts credentials and breaking signature changes as inline threads on the lines they touch. Bot settings show which credit pool pays for AI review and why it is paused.

Also on repowise.dev

• The indexing page follows the run: the clone shows under Reading the code, and the save stage reports what it is doing.
• Explore search matches near spellings.
• Repository pages answer at GitHub-style /owner/repo URLs.

Also in the open-source release

• search_codebase returns matching source lines, and get_context lists every edit site of a symbol, checked against the files on disk.
• repowise update --working-tree indexes uncommitted edits (a 2-file edit on a small repository refreshes in 4.5 s, from 12.5 s).
• repowise impacted-tests gains --prioritize and --explain; over 83 replayed failed PR runs, full-suite runs drop from 39 to 9 with no new misses.
• GitLab, Azure DevOps and Bitbucket are first-class git hosts in the CLI.
• repowise init sets up GitHub Copilot CLI and Kiro, and Cursor shell commands go through a hook.
• The local web UI is available in Simplified Chinese.
• PHP gets code health, and the security scan reads code, not text.

Upgrading

pip install --upgrade repowise

The first repowise update after upgrading re-scores, re-parses, rescans for security and re-renders structural pages once, with no model calls. On repowise.dev, a repository shows the new plans and scores after its next index.