repowise-dev

Bunch of pull request got merged today in @repowisedev 💁🏻 View it here: github.com/repowise-dev/repowise/pulls

Shipped a fix for @repowise: -files >2MB are no longer skipped during indexing! Concurrency was the memory bottleneck, not size so 2–8MB files now parse serially one by one. -Every symbol indexed and 50x faster docstring parsing. Link to PR: repowise#5294

@RepoWise -Collision proof section anchors & precise citations - Calibrated MCP ranking . Link: repowise#5269

2/ Ingestion: repeated methods in fluent call chains (#4849) - repowise#5255 3/ C#: awaited call assignments with ConfigureAwait (#4971) - repowise#5256

Worked on some issues last night and pushed fixes to @repowise today across language ingestion & code health! What was fixed: 1/ Kotlin: bare require/check resolution (#4968) - repowise#5254

Repowise - deterministic, zero-LLM code health scorer Hi folks, I maintain repowise, an open source tool that indexes a repo on your own machine and tells you which files are most likely to need the next bug fix, and what to do about them. Nothing leaves your box. Indexing and scoring make zero LLM calls, and the same commit gives the same score on every run, so you can put it in CI and trust it. After indexing, it checks itself against your own git history and prints the result. Something like "16 of the 20 lowest-health files had a bug fix in the last 6 months, 3.3x the 24% baseline." What you get from one index, served from localhost - - Every file scored 1-10 by 53 deterministic detectors (complexity, god classes, clones, untested hotspots, etc), split into defect risk, maintainability and performance. - Multi repo workspaces where it matches API contracts between your repos, so changing an endpoint shows which calls in other repos break - Dead code detection with confidence tiers - A dashboard with an architecture graph, a health bubble map of every file, and a generated wiki - An MCP server, so Claude Code, Cursor or a local agent reads the same index instead of grepping blind 28 languages parsed to an AST, including the old ones (COBOL, Delphi, C). Running it - pip install repowise, or Docker with the compose file in docker/. The only part that wants an LLM is the optional wiki prose, and Ollama with a local embedding model keeps that fully offline too. AGPL-3.0, about 7.9k stars, and 200+ contributors so far. Feedback and contributions welcome! Repo: repowise-dev/repowise Demo: repowise.dev

I built an open source codebase index for Claude Code Hey r/ClaudeCode, I'm one of the two people building Repowise, a free and open source codebase index made for Claude Code. Every Claude Code session starts by rediscovering your repo, grepping and opening files before it writes anything. Repowise indexes the codebase once (the call graph, git history, tests, docs) and keeps it current on every commit. Claude queries it over MCP, so before editing a file it can ask what depends on it, what usually changes with it, and how often it's broken before. It runs locally, your code never leaves your machine, and the engine needs no API key. Most tools in this space stop at the graph. A call graph tells an agent what connects to what, but it can't say which file breaks every other week, which tests actually reach the code you're changing, who owns it, or which files always change together without any import linking them. Repowise layers git history, test coverage, ownership and code health on top of the graph (parsed from 27 languages), and then checks the change after the agent makes it. The graph is the starting point, and the rest is what makes an agent's edit safer. What's new since I last posted: Code health now ties into refactoring - Instead of a list of warnings, you get one ranked queue across bugs, maintainability and performance, each item with the steps to fix it and the tests to run afterwards. Ask Claude to clean up the codebase and it starts from the top of that queue. Workspaces - Group your frontend, backend and shared libraries, and Repowise matches the API routes, queues and database tables between them, so Claude can see which other service breaks when you change an endpoint. CI support - repowise impacted-tests runs only the tests a change needs and falls back to the full suite when it isn't sure. Change Records - Every merged commit becomes a record with its owners, reaching tests and health delta, and repowise check fails CI when a change breaks your own policy file. Try it free. It's free and open source (AGPL), and the steps are - pip install repowise cd your-repo repowise init init connects it to Claude Code. Issues and contributions most welcome Repo: github.com/repowise-dev/repowise (7.8k stars)

I built an open source codebase index for Codex Hey r/codex, I'm one of the two people building Repowise, a free and open source codebase index for coding agents like Codex. Every agent session starts by rediscovering your repo, grepping and opening files before it writes anything. Repowise indexes the codebase once (the call graph, git history, tests, docs) and keeps it current on every commit. Codex queries it over MCP, so before editing a file it can ask what depends on it, what usually changes with it, and how often it's broken before. It runs locally, your code never leaves your machine, and the engine needs no API key. Most tools in this space stop at the graph. A call graph tells an agent what connects to what, but it can't say which file breaks every other week, which tests actually reach the code you're changing, who owns it, or which files always change together without any import linking them. Repowise layers git history, test coverage, ownership and code health on top of the graph (parsed from 27 languages), and then checks the change after the agent makes it. The graph is the starting point, and the rest is what makes an agent's edit safer. What's new since I last posted: Code health now ties into refactoring - Instead of a list of warnings, you get one ranked queue across bugs, maintainability and performance, each item with the steps to fix it and the tests to run afterwards. Ask your agent to clean up the codebase and it starts from the top of that queue. Workspaces - Group your frontend, backend and shared libraries, and Repowise matches the API routes, queues and database tables between them, so your agent can see which other service breaks when you change an endpoint. CI support - repowise impacted-tests runs only the tests a change needs and falls back to the full suite when it isn't sure. Change Records - Every merged commit becomes a record with its owners, reaching tests and health delta, and repowise check fails CI when a change breaks your own policy file. Try it free. It's free and open source (AGPL), and the steps are - pip install repowise cd your-repo repowise init init connects it to your agent. Issues and contributions most welcome Repo: repowise-dev/repowise (7.8k stars)

Repowise GitHub Overview: Local Codebase Intelligence for Dependency Graphs and Change Risk repowise by repowise-dev: repowise-dev/repowise Repowise is a local codebase intelligence layer for developers and AI coding assistants. It builds a structured view of dependency relationships, Git history, tests, architectural context and code-health signals on the host machine. The overview follows the problem of understanding large codebases, the local prerequisites and privacy boundary, the CLI and indexing workflow, caller confidence tiers, dead-code traversal, change-risk signals, inferred test reach and the operational cautions around the hidden .repowise directory. The source describes Python 3.11+ for the indexing engine, Node.js 20+ for the dashboard, and execution inside an active Git repository. With the local-only route, --no-prose avoids external model calls while the index is built from source structure and Git history. The result is a practical map for asking which components depend on a change, which files may be missing from a co-change, and which tests are structurally relevant. TimeStamps: 0:00 Why localized code changes create system-wide risk 0:42 Prerequisites and the local execution boundary 1:05 CLI installation and isolated environment setup 1:53 Offline indexing, serving, and diagnostic checks 2:45 Caller graphs and confidence tiers 3:19 Change risk, blast radius, and missing co-changes 3:57 Inferred test reach without full runtime coverage 4:28 Local intelligence database and security caution 4:51 Git worktrees and keeping .repowise out of remotes 5:12 Operational limitations and the final health diagnostic 🧩 Dependency graphs replace sequential text search with structural context 🔒 Local indexing keeps source analysis inside the repository environment 🧭 Confidence tiers distinguish exact, heuristic and inferred connections 🧪 Risk and test-reach views connect code changes to validation Repowise is most useful when you need architectural visibility before changing a repository: inspect callers, understand likely blast radius, trace relevant tests and keep the local index protected. Treat confidence tiers and worktree behavior as operational context, and verify the repository's own current documentation before adopting commands or configuration details. #Repowise #CodebaseIntelligence #SoftwareArchitecture