repowise

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

Some good amount of PR's merged in open source Have a look here: github.com/repowise-dev/repowise/pulls

🚀 ToolRadarr #127 — Repowise 🧠 Help AI coding agents understand your codebase before changing it. ⚡ Dependency graphs ⚡ Git history & code health ⚡ Change-risk insights ⚡ MCP integration 🔗 repowise-dev/repowise #ToolRadarr #AICoding #MCP t.co

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)

今週のPython Trendingから、agentのコードbase調査を助けるlocal index。 Repowiseはcode・call graph・git history・tests・docs・design decisionsをローカルで索引化。「何がこのfunctionを呼ぶか」「ここを変えると何が壊れるか」をagentから検索できます。 repowise-dev/repowise

Repowise: Understand your codebase without paying your agent to rediscover it (7k stars) What it does All text below is quoted directly from the project README. >Repowise indexes your code, call graph, git history, tests, docs and design decisions once, on your machine. Then you and your coding agent ask it things: what calls this, what breaks if I change it, what is dead, what to fix first, and why it was built this way. Graph, risk, health, tests and dead code make zero LLM calls · no API key needed · free and self-hosted · AGPL-3.0 or commercial What it does: One index, three ways to use it. - How does checkout work in this repo? A cited answer built from the call graph and the generated docs, in one call. - What calls this function, and what does it call? A call graph across 26 parsed languages, every edge stamped with how it was resolved and how far to trust it, plus traced execution flows from each entry point. - Can I get docs for this codebase? A wiki for every module and file, rendered from the code's structure with no key, or written by a model when you choose. It updates incrementally after each commit. - Which of our docs are wrong? Markdown checked against the tree: every reference to a file or symbol the code no longer has, with the line to edit. - Why is it built this way? Decisions mined from ADRs, # WHY: comments, commit and PR history and your agent sessions, each tied to the code it governs and flagged when it goes stale. - Who knows this code? Owners, bus factor, knowledge-loss risk when the main author goes quiet, and suggested reviewers. - What breaks if I change this? Symbol-level blast radius: the callers of what you changed, the files that historically change with it but are missing from your diff, and the tests that reach it. - Which tests should run? The tests a diff actually exercises, from a coverage report if you have one and from the call graph if you do not. >Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste: Read https://docs.repowise.dev/setup.md and set up Repowise in this repository. Repository repowise-dev/repowise Repository stats |Metric|Value| |:-|:-| |Stars|7,203| |Forks|788| |Last release|v0.55.0 (2026-10-04)| |Languages|Python 79.1%, TypeScript 20.1%, Tree-sitter Query 0.4%| |Contributors|117| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|Claude: 5, Codex: 1, Cursor: 2, Copilot: 2| |AI co-authored commits|Claude: 5, Codex: 1, Cursor: 2, Copilot: 1| Main contributor |Field|Value| |:-|:-| |Name|Raghav Chamadiya| |GitHub|@RaghavChamadiya| |Commits to this repo|1,616 (top contributor)| |Bio|I build AI tools for engineers. repowise (codebase intelligence) + Thita.ai (20k users).| |Company|Repowise| |Website|repowise.dev| |X / Twitter|@RaghavChamadiya| |Followers|139| |Public repos|26| |On GitHub since|2020-05-15|

I quit my job to build an open source tool with my wife, and it's at 7.2k GitHub stars My wife and I always wanted to build something together, so for a long time we shipped side projects on nights and weekends. One of them reached 25k users, but neither of us wanted to leave a stable job for it. Then I spent months watching coding agents work. I'd been building with LLMs since 2023 and owned the AI architecture at my company, and I kept seeing an agent grep the same file four times in one session and still have no idea which parts of the codebase were fragile or why the code was written that way. All of that information already lives in the repo, just not in a form an agent can use. We started building something for it, and about 2.5 months ago I resigned to work on it full time. It's called Repowise. It indexes your repo once and serves it to your agent over MCP as five layers - a dependency graph, git history, generated docs, architectural decisions, and a code health scores with no LLM involved. In our benchmark against four other tools and a bare agent, it used 31% fewer output tokens over a full 48-question run, saved about 97% on a single context load, and had the best gold-file coverage on retrieval. It's now at 7.2k GitHub stars, over 100k PyPI downloads, and 110+ contributors, which still amazes me. We never did outbound. We just shipped code, wrote about what we were learning, and people found it. Enterprise teams and investors started reaching out on their own, and we're now raising our seed round. If you use Claude Code, Cursor, or any other agent over MCP, please run it on a real repo and tell me what breaks. Issues and PRs are open, and you can comment on any issue to pick it up. If you're early in your career and not sure where to start, message me and I'll point you at something. Happy to answer any questions Repo: repowise-dev/repowise

I built Repowise, an open source codebase index for Claude Code. Here's what's new Hey r/ClaudeAI, I'm one of the two people building Repowise, a free and open source tool made specifically 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. How Claude Code fits into building it- we build Repowise with Claude Code every day, and Claude Code runs on the Repowise repo with Repowise connected. Most features started as something we watched it struggle with. It would read the same file three times, miss the test that always changes with the file it was editing, or not know a change would break another service. Each of those turned into a tool it can call. When a feature lands, the first test is whether Claude actually uses it unprompted in a real session. What's new since I last posted: Lens, a mod for Claude Code - It shows a map of your repo that lights up as Claude reads and edits files, plus a quick review of what changed after each turn. It reads the local index, adds no model calls and never gets in Claude's way. We built it because we wanted to see what Claude was actually looking at. 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. Coverage, security and stale-docs checks run from one GitHub Action. 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: repowise-dev/repowise

A claude code mod that shows every file an edit touches Repowise is an open source tool that indexes your codebase - call graph, git history, tests and code health. Coding agents can query it instead of grepping around. We just shipped Lens, which uses the new Claude Code mods to show you that index while Claude works. Type /lens and you get a map of your repo. Files light up as Claude searches, reads and edits them. When Claude edits a file, every file that imports it lights up too. In the video, a one-line comment in Django's query.py lights up 12 files, and conf/init.py lights up about 248. The Flow tab gives you a short list for each edited file: what the change reaches that Claude never opened, the files that usually change with it, and the tests that cover it. After an edit, a review row shows the health change and the tests to run, and one button sends those tests to Claude. Lens makes no model calls of its own, and it never blocks or approves anything Claude does. Setup: /plugin marketplace add repowise-dev/repowise /plugin install repowise@repowise pip install repowise repowise init --no-prose --yes repowise serve --no-ui You need Claude Code 2.1.287+. Indexing runs locally and needs no API key. repowise-dev/repowise