Repowise (Hosted) changelog

https://www.repowise.dev/llms.txt

− - [Bot](https://repowise.dev/bot): The GitHub PR bot: free deterministic Signals comments, optional AI review on every pull request that changes code, and a Repowise review check on every push− - [repowise vs Qodo](https://repowise.dev/compare/qodo-alternative): Qodo is the stronger fit when you want enforced review standards learned from your own PR history, on GitHub, GitLab, Bitbucket or Azure DevOps. The repowise PR bot starts from the dependency graph and git history, comments without a model by default, and adds AI review as an option.− - [repowise vs Greptile](https://repowise.dev/compare/greptile-alternative): Greptile is the focused pick for LLM review backed by a repository graph, billed per review at $1 a credit with no seats, and it self-hosts on Enterprise. The repowise PR bot posts free graph and git-history signals first, with AI review optional.− - [repowise vs CodeRabbit](https://repowise.dev/compare/coderabbit-alternative): CodeRabbit is the direct fit when you want an AI reviewer on GitHub, GitLab, Azure DevOps or Bitbucket that comments line by line, runs 50+ linters and follows your feedback. The repowise PR bot scores change risk from the diff, the dependency graph and git history without a model, and the same index serves documentation, health and agent context outside the review.− - [repowise vs CodeGraph](https://repowise.dev/compare/codegraph-alternative): CodeGraph is a genuine measured competitor and the better fit when graph indexing speed and a narrow agent interface matter most. Repowise builds substantially more context and led the measured retrieval and agent-loop results, with the attached conditions.− - [repowise vs Graphify](https://repowise.dev/compare/graphify-alternative): Graphify is the stronger fit when your material is a mixture of code, documents and images, or when you want graph exports and graph-analysis commands such as communities, paths and reverse impact. In the repowise benchmark it indexed substantial repository structure, while its broad result sets traded precision for reach.− - [Comparisons](https://repowise.dev/blog/comparisons): 70 posts− - [Best AI Coding Agents in 2026: How They Handle a Large Codebase](https://repowise.dev/blog/comparisons/best-ai-coding-agents): The best AI coding agents in 2026 compared on pricing, where they run, MCP support and context, with repowise's published benchmarks on Claude Code and Codex.− - [Qodo Pricing in 2026: $0.012 a Credit, About $1.67 a Review, and What a Team Pays](https://repowise.dev/blog/comparisons/qodo-pricing): Qodo Pro Team costs $0.012 a credit, about $1.67 a review on its own pack estimates, so a 20-developer team pays about $4,000 a year for pull request review.− - [CodeRabbit Pricing in 2026: $24 a Developer, and What a 20-Dev Team Pays](https://repowise.dev/blog/comparisons/coderabbit-pricing): CodeRabbit costs $24 to $72 per developer a month billed annually, so 20 developers pay $5,760 a year on Essentials. Plans, seats, limits and overage.− - [Greptile Pricing in 2026: $1 a Credit, No Seat Fee, and What a Year Costs](https://repowise.dev/blog/comparisons/greptile-pricing): Greptile Pro costs $1 a credit with no seat fee, and a Base review is 1 credit, so 20 developers opening 10 PRs each a month pay about $2,400 a year.− - [AI Code Review Pricing Compared (2026): What 7 Tools Cost a Year for 5 to 200 Developers](https://repowise.dev/blog/comparisons/ai-code-review-pricing-compared): AI code review costs about $120 to $576 per developer a year on most tools and $1,800 or more on Claude Code Review, worked out for 5 to 200 developers.− - [Best AI Code Review Tools in 2026: 14 Compared on Price and Fit](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): AI code review compared: CodeRabbit, Greptile, Copilot, Bugbot, Claude, Qodo, Devin and more, with dated prices, git hosts and a pick-it-if line for each.− - [Best Architecture Documentation Tools in 2026: C4, ADRs and Diagrams](https://repowise.dev/blog/comparisons/best-architecture-documentation-tools): Structurizr, IcePanel, Mermaid, PlantUML, Eraser, Backstage TechDocs, Log4brains and repowise compared on C4 views, ADRs and keeping docs current with the code.− - [Best Code Health Tools in 2026: Five Compared](https://repowise.dev/blog/comparisons/best-code-health-tools-2026): CodeScene leads on hotspot analysis, SonarQube on quality gates and Codacy on PR checks. Five code health tools compared on pricing, scoring and fit.− - [Best Codebase Documentation Tools for AI Coding Agents (2026)](https://repowise.dev/blog/comparisons/best-codebase-documentation-tools-ai-agents): Seven tools for documenting a codebase for AI agents, compared on MCP access, freshness and private repos: repowise, DeepWiki, Code Wiki, Mintlify and more.− - [Best Code Visualization Tools in 2026: Graphs, Maps and Diagrams](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): Seven code visualization tools, from Madge and Structurizr to CodeScene and repowise, compared on what each draws from source code and what it costs.− - [Best Dead Code Detection Tools by Language (2026)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Dead code finders by language: Knip for TypeScript, Vulture for Python, deadcode for Go, PMD and Maven for Java, repowise for mixed repos. Commands included.− - [Best Dependency Graph Tools for Monorepos in 2026](https://repowise.dev/blog/comparisons/best-dependency-graph-tools-monorepos): Nx, Turborepo, Madge, dependency-cruiser, Knip and repowise compared on how each draws the graph, finds circular dependencies and shows what a change touches.− - [Git Analytics Tools: Code-Level and Team-Level, Compared](https://repowise.dev/blog/comparisons/best-git-analytics-tools): Six git analytics tools compared: CodeScene and repowise for hotspots, ownership and bus factor, Swarmia and LinearB for team metrics, with October 2026 prices.− - [Best GitHub PR Review Bots in 2026: 6 Compared With Pricing](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): The best PR bots for GitHub in 2026: CodeRabbit, Greptile, Copilot code review, Codacy, Reviewdog and repowise compared on price, noise and repo context.− - [Best MCP Servers for Coding Agents in 2026](https://repowise.dev/blog/comparisons/best-mcp-servers-coding-agents): The best MCP servers for coding agents: repowise for codebase context, Context7 for docs, GitHub for PRs, Playwright for browsers, with a stack by use case.− - [Best Refactoring Tools in 2026: What to Fix First and How](https://repowise.dev/blog/comparisons/best-refactoring-tools): The best refactoring tools rank what to fix first, then help you change it safely: CodeScene, SonarQube, CAST Imaging, Moderne, JetBrains and repowise compared.− - [Best Static Analysis Tools in 2026, Compared for Large Codebases](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): Static analysis tools compared for large codebases: SonarQube, Semgrep, CodeQL, Coverity, Snyk Code, DeepSource, Codacy, free linters and repowise, with pricing.− 4,246 public repositories are indexed and browsable. Each repository serves the same seven pages: /overview (health, hotspots, structure), /architecture (dependency graph and layered C4 view), /code-health (code health, hotspots, coverage, dead code), /docs (generated documentation), /commits (per-commit change risk), /owners (ownership and bus factor), and /decisions (architectural decision records mined from history). Append the path to any repository URL.+ Setting up Repowise Hosted (repowise.dev) for a user? Follow https://docs.repowise.dev/hosted/setup.md: sign-in, indexing, MCP over OAuth, the PR bot and coverage, with no key in chat.+ - [Bot](https://repowise.dev/bot): The GitHub PR bot: free deterministic risk, coverage and health checks, optional AI review on every pull request that changes code, and a Repowise review check on every push+ - [State of open-source code health 2026](https://repowise.dev/research/code-health-2026): 195 GitHub repositories with 1,000+ stars: hotspots, bug-fix concentration, dead code, circular import chains, hub files, bus factor and tests, with method and tables+ - [repowise vs Qodo](https://repowise.dev/compare/qodo-alternative): Qodo is the stronger fit when you want enforced review standards learned from your own PR history, on GitHub, GitLab, Bitbucket or Azure DevOps. The Repowise PR bot starts from the dependency graph and git history, comments without a model by default, and adds AI review as an option.+ - [repowise vs Greptile](https://repowise.dev/compare/greptile-alternative): Greptile is the focused pick for LLM review backed by a repository graph, billed per review at $1 a credit with no seats, and it self-hosts on Enterprise. The Repowise PR bot posts free graph and git-history checks first, with AI review optional.+ - [repowise vs CodeRabbit](https://repowise.dev/compare/coderabbit-alternative): CodeRabbit is the direct fit when you want an AI reviewer on GitHub, GitLab, Azure DevOps or Bitbucket that comments line by line, runs 50+ linters and follows your feedback. The Repowise PR bot scores change risk from the diff, the dependency graph and git history without a model, and the same index serves documentation, health and agent context outside the review.+ - [repowise vs CodeGraph](https://repowise.dev/compare/codegraph-alternative): CodeGraph is a genuine measured competitor and the better fit when graph indexing speed and a narrow agent interface matter most. Repowise builds substantially more context and led the measured retrieval and agent-loop results.+ - [repowise vs Graphify](https://repowise.dev/compare/graphify-alternative): Graphify is the stronger fit when your material is a mixture of code, documents and images, or when you want graph exports and graph-analysis commands such as communities, paths and reverse impact. In the Repowise benchmark it indexed substantial repository structure, while its broad result sets traded precision for reach.+ - [Comparisons](https://repowise.dev/blog/comparisons): 71 posts+ - [Best Claude Code Skills in 2026: Seven Skill Repos Worth Installing](https://repowise.dev/blog/comparisons/best-claude-code-skills): The best Claude Code skills in 2026, from engineering workflows to security audits and UI cleanup, with install commands for Claude, Codex and agent skills.+ - [Best AI Coding Agents in 2026: How They Handle a Large Codebase](https://repowise.dev/blog/comparisons/best-ai-coding-agents): The best AI coding agents in 2026: Claude Code, Codex, Cursor and Copilot compared on pricing, where they run, MCP support and large-codebase context.+ - [Qodo Pricing in 2026: $0.015 a Credit, About $2.14 a Review, and What a Team Pays](https://repowise.dev/blog/comparisons/qodo-pricing): Qodo Pro Team costs $0.015 a credit, about $2.14 a review on its own pack estimates, so a 20-developer team pays about $5,140 a year for pull request review.+ - [CodeRabbit Pricing in 2026: $24 to $72 a Developer, and What a 20-Dev Team Pays](https://repowise.dev/blog/comparisons/coderabbit-pricing): CodeRabbit costs $24, $48 or $72 per developer a month billed annually ($30, $60, $90 monthly). Public repos are free; 20 devs pay $5,760 a year.+ - [Greptile Pricing in 2026: $1 a Credit, No Seat Fee, and What a Year Costs](https://repowise.dev/blog/comparisons/greptile-pricing): Greptile Pro costs $1 a credit with no seat fee. A Base review is 1 credit, Plus 3 and Apex 10, so 20 devs at 10 PRs a month pay about $2,400 a year.+ - [AI Code Review Pricing Compared (2026): What 7 Tools Cost a Year for 5 to 200 Developers](https://repowise.dev/blog/comparisons/ai-code-review-pricing-compared): Most AI code review costs $1 to $25 a review or $19 to $48 a seat as of November 2026, about $120 to $576 per developer a year. Worked for 5 to 200 devs.+ - [Best AI Code Review Tools in 2026: 14 Compared on Price and Fit](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): The best AI code review tools in 2026 are CodeRabbit, Greptile and GitHub Copilot code review. 14 tools compared on price, context, git hosts and BYOK.+ - [Best Architecture Documentation Tools in 2026: C4, ADRs and Diagrams](https://repowise.dev/blog/comparisons/best-architecture-documentation-tools): Nine architecture documentation tools compared on C4 views, ADRs, price and staying current, with data from 195 repos on how fast code outruns diagrams.+ - [Best Code Health Tools in 2026: Five Compared](https://repowise.dev/blog/comparisons/best-code-health-tools-2026): CodeScene, SonarQube, Codacy, Qlty and repowise compared on scoring, hotspots, MCP and price, with code health scores from 195 popular open-source repos.+ - [Best Codebase Documentation Tools for AI Coding Agents (2026)](https://repowise.dev/blog/comparisons/best-codebase-documentation-tools-ai-agents): Eight tools that document a codebase for AI coding agents, compared on MCP access, freshness and private repos, with data on why hubs and owners matter.+ - [Best Code Visualization Tools in 2026: Graphs, Maps and Diagrams](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): Seven code visualization tools compared on what each draws from source code and what it costs, plus what a map must show, from 195 real repos.+ - [Best Dead Code Detection Tools by Language (2026)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Knip for TypeScript, Vulture for Python, deadcode for Go, PHPStan for PHP and repowise for mixed repos. We found dead code in 96% of 190 popular repos.+ - [Best Dependency Graph Tools for Monorepos in 2026](https://repowise.dev/blog/comparisons/best-dependency-graph-tools-monorepos): Nx, Turborepo, Madge, dependency-cruiser, Knip and repowise compared, with data from 195 repos: 89% have circular import chains between files.+ - [Git Analytics Tools: Code-Level and Team-Level, Compared](https://repowise.dev/blog/comparisons/best-git-analytics-tools): Ten git analytics tools compared with November 2026 prices, plus data from 195 repos: 10% of files take 68% of churn and 60% have one main author.+ - [Best GitHub PR Review Bots in 2026: 8 Compared With Pricing](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): The best PR review bots for GitHub in 2026 are CodeRabbit, Greptile and Copilot code review for AI review, and repowise or Reviewdog for repeatable checks.+ - [Best MCP Servers in 2026: Coding Agents and Awesome Lists](https://repowise.dev/blog/comparisons/best-mcp-servers-coding-agents): The best MCP servers in 2026 for coding agents, from Context7 and GitHub to Playwright and repowise, plus the awesome MCP servers lists to find more.+ - [Best Refactoring Tools in 2026: What to Fix First and How](https://repowise.dev/blog/comparisons/best-refactoring-tools): IDE refactorings, AI agents, Moderne, CodeScene and repowise compared. In 173 popular repos, the least-healthy 20% of files held 60% of bug-fixed files.+ - [Best Static Analysis Tools in 2026, Compared for Large Codebases](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): SonarQube, Semgrep, CodeQL, Snyk Code, Veracode, Coverity and free linters compared on price and depth, plus data from 195 large repos on where risk sits.+ 4,032 public repositories are indexed and browsable. Each repository serves the same seven pages: /overview (health, hotspots, structure), /architecture (dependency graph and layered C4 view), /code-health (code health, hotspots, coverage, dead code), /docs (generated documentation), /commits (per-commit change risk), /owners (ownership and bus factor), and /decisions (architectural decision records mined from history). Append the path to any repository URL.+ Repo pages for agents: https://repowise.dev/repo/{owner}/{name}.md (or the page URL with `Accept: text/markdown`) gives what the repo is, how to install it, how it works, code health and maintenance, as of an indexed commit.

description

Hosted codebase intelligence for repos indexed on repowise.dev — no local indexing needed. → Ask how your codebase works. Hosted codebase intelligence for repos indexed on repowise.dev.

remote_url

https://api.repowise.dev/mcp/{owner}/{repo} → https://api.repowise.dev/mcp

repository_url

— → https://github.com/repowise-dev/repowise

version

0.17.1 → 1.0.0

https://www.repowise.dev/llms.txt

− - [Bot](https://repowise.dev/bot): The GitHub PR bot that posts deterministic code-health comments on every pull request− - [Who Wrote This?](https://repowise.dev/resources/ai-governance): The engineering leader's guide to governing AI-written code, and the technical debt that comes with it− - [repowise vs Qodo](https://repowise.dev/compare/qodo-alternative): Qodo is the more direct purchase for automated pull-request feedback. Repowise is designed to supply durable repository evidence before and during review, not replace the review agent itself.− - [repowise vs Greptile](https://repowise.dev/compare/greptile-alternative): Greptile is the focused choice when contextual pull-request review is the job. Repowise exposes its repository graph, history, health, decisions, and documentation as inspectable outputs for both humans and agents.− - [repowise vs CodeRabbit](https://repowise.dev/compare/coderabbit-alternative): CodeRabbit is the direct fit for line-by-line AI review comments on every pull request. Repowise's PR bot scores change risk from the diff, the dependency graph and git history, and the same index serves documentation, health and agent context outside the review.− - [repowise vs Graphify](https://repowise.dev/compare/graphify-alternative): Graphify is compelling when graph communities, hubs, and paths are the desired primitives. In the Repowise benchmark it indexed substantial repository structure, while its broad result sets traded precision for reach.− - [Code Health: The Complete Guide to Defect-Validated Code Quality](https://repowise.dev/guides/code-health): How repowise scores every file from 1 to 10 with 25 deterministic markers, why the score predicts real bugs, and how to turn it into a ranked worklist you act on the same day.− - [Decisions & ADRs: Capture the Why Your Code Was Shaped This Way](https://repowise.dev/guides/decisions-adr): How repowise mines architecture decisions from eight sources, backs each with evidence spans, links them to the dependency graph, ages them as the code changes, and serves the rationale over MCP via get_why.− ## Documentation− - [Auto-sync](https://docs.repowise.dev/auto-sync): Six ways to keep your repowise index current: a post-commit hook, a file watcher, GitHub, GitLab and Gitea or Forgejo webhooks, and a polling safety net.− - [Build on Repowise](https://docs.repowise.dev/build-on-repowise): The surfaces a tool, service or agent can build on, how each one authenticates, and which contracts are versioned and stable across releases.− - [Gates in CI](https://docs.repowise.dev/ci): Gate pull requests in CI on patch coverage, new doc drift, new security findings, new code-health findings and change risk, enforce a change policy, and run only the tests needed.− - [Contributing](https://docs.repowise.dev/contributing): How to build and test the open-source Repowise repository, find something to work on, claim an issue, and open a pull request.− - [Local dashboard](https://docs.repowise.dev/dashboard): The self-hosted repowise dashboard reads your local index to answer architecture, health, ownership and history questions, with nothing leaving your machine.− - [Enterprise](https://docs.repowise.dev/enterprise): repowise for platform, AppSec and architecture leads: change and component evidence computed inside your network, and what the commercial licence adds.− - [Welcome to repowise](https://docs.repowise.dev): repowise indexes your repository into five intelligence layers and serves them to your AI coding agent through MCP tools, so it reads answers, not code.− - [Licensing](https://docs.repowise.dev/licensing): repowise is AGPL-3.0. What that allows, why internal use creates no obligation to publish your code, and when a company needs a commercial licence.− - [Roadmap](https://docs.repowise.dev/roadmap): What we are building next across languages, source control beyond git, multi-repo, integrations and core intelligence, plus what we have decided not to build.− - [Security & data handling](https://docs.repowise.dev/security): What Repowise processes, what it persists, what leaves your machine under each deployment mode, and how to reduce that to zero.− - [Upgrading](https://docs.repowise.dev/upgrading): Upgrade the repowise package, run repowise update, and your existing index keeps working. No reindex in the normal case, and a full reindex is never forced.− - [Git worktrees](https://docs.repowise.dev/worktrees): Index a linked git worktree without re-indexing from scratch, by seeding from the base checkout and catching up incrementally.− - [Agents: add, remove, refresh](https://docs.repowise.dev/cli/agents): Wire repowise into Claude Code, Codex, Cursor, VS Code, OpenCode, Hermes, GitHub Copilot CLI or Kiro, or drop the config snippet for anything else.− - [Change evidence: changes, check, suspects, report, events](https://docs.repowise.dev/cli/changes): Change Records rebuilt from git with an evidence checklist, plus repowise check for change policy, suspects for a symptom, evidence reports and events.− - [Components, packages and attribution](https://docs.repowise.dev/cli/components): Declare Backstage-shaped components with owners checked against recent activity, export package usage as CycloneDX, and read three-state AI attribution.− - [Decisions: capture, review, govern](https://docs.repowise.dev/cli/decision): Record architectural decisions so the why survives the team. Review the candidates capture proposed, accept the ones that should govern, and keep them in git.− - [Distill: compact command output](https://docs.repowise.dev/cli/distill): repowise distill renders noisy command output errors-first and fully reversible, saving 61 to 89% of tokens in measured runs on tests, git log and git diff.− - [Coverage and CI gates: coverage, impacted-tests, doc-drift, security check, health check](https://docs.repowise.dev/cli/gates): Flags for ingesting coverage, gating a change on patch coverage, selecting the tests a change needs, and the doc-drift, security and health gates.− - [Code health: health, risk](https://docs.repowise.dev/cli/health): repowise health scores every file on defect risk, maintainability and performance; repowise risk ranks a commit or diff range against recent commits.− - [Hooks: auto-sync on commit](https://docs.repowise.dev/cli/hook): Install, check and remove the post-commit git hook that runs repowise update after every commit, and see hook stats on what your agent hooks fired.− - [Indexing: init, update, reindex](https://docs.repowise.dev/cli/indexing): repowise init builds the intelligence layers from scratch, update keeps them current on each commit, and reindex rebuilds the vector store with no LLM.− - [Other commands](https://docs.repowise.dev/cli/other): One-shot repowise utilities including costs, next, overlap, dead-code, security scan, doctor, whats-new, export, telemetry, login, publish and delete.− - [CLI overview](https://docs.repowise.dev/cli/overview): Every repowise CLI command at a glance, from init, update and serve to search, health, risk, distill and decision, with a link to each command's full guide.− - [Query: search, ask, context, symbol, why, status](https://docs.repowise.dev/cli/query): Search the docs, ask cited questions, read triage cards and symbols, trace why code exists, and check sync state from the terminal with repowise search.− - [Server & watch: serve, watch, mcp](https://docs.repowise.dev/cli/server): Run repowise serve for the API and local dashboard, repowise watch to auto-update on file save, or repowise mcp to expose the MCP server to your editor.− - [Uninstall: remove repowise](https://docs.repowise.dev/cli/uninstall): Remove repowise from this repo, and optionally from this machine, with a full inventory of every path it wrote and a report of what was removed and kept.− - [Workspace: multi-repo commands](https://docs.repowise.dev/cli/workspace): Manage repos in a repowise workspace: list, add, remove, scan, set the default, explain contract links, lint architecture rules and read architecture metrics.− - [Set up with your agent](https://docs.repowise.dev/getting-started/for-agents): Paste one line into Claude Code, Codex, Cursor or any coding agent and it installs repowise, indexes the repo, connects the MCP tools and asks one question.− - [How it works](https://docs.repowise.dev/getting-started/how-it-works): How repowise builds its index in five passes (dependency graph, git history, wiki, decision records and code health) and how the MCP tools query the result.− - [Agent plugins](https://docs.repowise.dev/getting-started/plugins): The Claude Code and Codex plugins bundle the repowise MCP server, lifecycle hooks, skills and slash commands into one install. See what each ships.− - [Quickstart](https://docs.repowise.dev/getting-started/quickstart): Install repowise, index your repo with no API key, open the dashboard and connect your agent. Self-hosted, hosted (repowise.dev), or a multi-repo workspace.+ Setting up Repowise for a user? Follow https://docs.repowise.dev/setup.md, a step-by-step runbook written for coding agents.+ Evaluating Repowise for a company? Start with the Evaluating Repowise section below.+ Docs pages and the pricing page are also served as Markdown: append `.md` to the URL, or request it with `Accept: text/markdown`.+ ## Evaluating Repowise+ - [Pricing](https://repowise.dev/pricing.md): Every plan's monthly and yearly price, what each includes, the full comparison, and how code is handled+ - [Security & data handling](https://docs.repowise.dev/security.md): What Repowise processes, what it persists, what leaves your machine under each deployment mode, and how to reduce that to zero.+ - [Hosted security and data handling](https://docs.repowise.dev/hosted/data-handling.md): A security reviewer's guide to Hosted at repowise.dev, covering what happens to your source code, what is kept, when a model sees it, and how data is deleted.+ - [Hosted vs self-hosted](https://docs.repowise.dev/hosted/vs-self-hosted.md): Hosted and self-hosted repowise ship the same intelligence layers, MCP tools and dashboard. They differ in ops, billing and team features, not agent power.+ - [Licensing](https://docs.repowise.dev/licensing.md): repowise is AGPL-3.0. What that allows, why internal use creates no obligation to publish your code, and when a company needs a commercial licence.+ - [Enterprise](https://docs.repowise.dev/enterprise.md): repowise for platform, AppSec and architecture leads: change and component evidence computed inside your network, and what the commercial licence adds.+ - [Benchmarks](https://docs.repowise.dev/reference/benchmarks.md): The headline measurements with their samples, the scale table with lines of code, the rows we lose, and where the full methodology and raw runs live.+ - [Security policy](https://repowise.dev/legal/security): Encryption, access control, incident response and compliance status+ - [Privacy policy](https://repowise.dev/legal/privacy): What personal data Repowise Hosted collects and how it is used+ - [Terms of service](https://repowise.dev/legal/terms): The terms that govern use of Repowise Hosted+ - [Enterprise security review](https://docs.repowise.dev/enterprise.md#security-review-for-enterprise): Residency, subprocessors, model training, SLA, certifications, SSO, DPA and indemnity, answered for Enterprise+ - [Benchmark results](https://repowise.dev/benchmarks): Retrieval, token, call-graph and code-health results, with method and raw runs+ - Enterprise runs entirely inside your perimeter: Repowise never handles your code or data, so your own controls and certifications cover the deployment.+ - Security reviews, DPAs and questionnaires: security@repowise.dev or hello@repowise.dev+ - [Bot](https://repowise.dev/bot): The GitHub PR bot: free deterministic Signals comments, optional AI review on every pull request that changes code, and a Repowise review check on every push+ - [AI code review cost calculator](https://repowise.dev/tools/ai-code-review-cost-calculator): Yearly cost of repowise, CodeRabbit, Greptile, Qodo, Copilot, Cursor Bugbot and Claude Code Review for a team, from dated list prices+ - [Codex MCP server for codebase context](https://repowise.dev/integrations/codex): Give Codex full context of a large codebase: 10 MCP tools over your code graph, git history and decisions, session hooks and a managed AGENTS.md. Open source.+ - [Cursor MCP server for codebase context](https://repowise.dev/integrations/cursor): Give Cursor full context of a large codebase: 10 MCP tools over your code graph, git history and decisions, an always-on rule and a distill hook. Open source.+ - [GitHub Copilot MCP server for codebase context](https://repowise.dev/integrations/github-copilot): Give GitHub Copilot in VS Code and Copilot CLI full context of a large codebase: 10 MCP tools over your code graph, git history and decisions. Open source.+ - [MCP server for Cline, Windsurf, Gemini CLI, Zed](https://repowise.dev/integrations/mcp-clients): One MCP server gives OpenCode, Kiro, Cline, Windsurf, Gemini CLI and Zed full codebase context: 10 tools over your code graph, git history and decisions.+ ## Documentation+ - [Docs index](https://docs.repowise.dev/llms.txt): Every docs page, titled, described and linked as Markdown+ - [Agent setup runbook](https://docs.repowise.dev/getting-started/setup.md): The step-by-step runbook a coding agent follows to install repowise, index the current repository, connect the MCP tools and report back, readable by anyone.+ - [Quickstart](https://docs.repowise.dev/getting-started/quickstart.md): Install repowise, index your repo with no API key, open the dashboard and connect your agent. Self-hosted, hosted (repowise.dev), or a multi-repo workspace.+ - [Set up with your agent](https://docs.repowise.dev/getting-started/for-agents.md): Paste one line into Claude Code, Codex, Cursor or any coding agent and it installs repowise, indexes the repo, connects the MCP tools and asks one question.+ - [Install repowise](https://docs.repowise.dev/installation/install.md): Install the repowise CLI on macOS, Linux, or Windows via pip or uv. Verify, upgrade, switch versions, or uninstall. Every step.+ - [MCP tools: overview](https://docs.repowise.dev/mcp/overview.md): The curated set of task-shaped MCP tools repowise exposes to Claude Code and any MCP agent, batched to collapse long tool-call chains into one round-trip.+ - [CLI overview](https://docs.repowise.dev/cli/overview.md): Every repowise CLI command at a glance, from init, update and serve to search, health, risk, distill and decision, with a link to each command's full guide.+ - [Workspace setup](https://docs.repowise.dev/multi-repo/workspace-setup.md): Index related git repos as one repowise workspace for cross-repo co-changes, API contract matching and federated MCP queries on top of per-repo intelligence.+ - [Gates in CI](https://docs.repowise.dev/ci.md): Gate pull requests in CI on patch coverage, new doc drift, new security findings, new code-health findings and change risk, enforce a change policy, and run only the tests needed.+ - [Hosted platform](https://docs.repowise.dev/hosted/overview.md): What the managed platform adds to the OSS engine: zero-ops indexing, push-sync, AI docs and chat, a security suite, team portfolio intelligence and alerting.+ - [Who Wrote This?](https://repowise.dev/resources/ai-governance): The engineering leader's guide to governing AI-written code, and the technical debt that comes with it. The AI code governance guide, with an AI coding policy template+ - [Chapter 1: Your codebase has a new author](https://repowise.dev/resources/ai-governance/your-codebase-has-a-new-author): how widely teams use AI coding tools, how little they trust the output, and why few can say which code an agent wrote.+ - [Chapter 2: Debt at agent speed](https://repowise.dev/resources/ai-governance/debt-at-agent-speed): agent-era open-source projects carry about 4.5 times the share of too-big functions at the same age. What we measured and what to do on Monday.+ - [Chapter 3: Who wrote this?](https://repowise.dev/resources/ai-governance/who-wrote-this): read commit trailers, agent config files and edit capture to record which agent wrote each change, report label coverage, and keep Change Records.+ - [Chapter 4: Reviewing at agent speed](https://repowise.dev/resources/ai-governance/reviewing-at-agent-speed): contributors to agent-era projects add over three times as much code a week. Point review at code with a fix history and run the tests it reaches.

Showing the first 40 of each.

https://www.repowise.dev/llms.txt

− - [AI provenance](https://repowise.dev/features/agent-provenance): Know which code AI wrote, and if it is healthy− - [Architecture & Dependency Graph: The Complete Guide to Diagrams Derived From Code](https://repowise.dev/guides/architecture): How repowise parses your repo into one directed dependency graph across 16 languages, ranks it with centrality, and derives browsable C4 and knowledge-graph views with no LLM in the layout path.− - [Agent Provenance: The AI-Debt Radar for AI-Written Code](https://repowise.dev/guides/agent-provenance): How repowise attributes commits to the AI agents that wrote them and fuses that with a defect-validated health score and bus-factor ownership to rank the AI-written code most likely to break.− - [Auto-sync](https://docs.repowise.dev/auto-sync): Five ways to keep your repowise wiki current as code changes: post-commit hook, file watcher, GitHub webhook, GitLab webhook, and a polling safety net.− - [Gates in CI](https://docs.repowise.dev/ci): Fail a pull request on low patch coverage, new documentation drift, new security findings or unusual change risk, and run only the tests it needs. No index and no API key.− - [Local dashboard](https://docs.repowise.dev/dashboard): The self-hosted web dashboard that reads your .repowise index and answers architecture, health, ownership and history questions without sending anything off your machine.− - [Enterprise](https://docs.repowise.dev/enterprise): For companies that need Repowise on their own infrastructure or under commercial terms. What the commercial licence adds, what is available today, and how on-premise deployment works.− - [Welcome to repowise](https://docs.repowise.dev): Repowise indexes your repository into five intelligence layers and serves them to your AI coding agent through its MCP tools, so the agent reads an answer instead of re-reading your codebase. Self-hosted or hosted, same engine.− - [Licensing](https://docs.repowise.dev/licensing): Repowise is AGPL-3.0. What that allows, when a company needs a commercial licence, what the commercial licence covers, and what the hosted service runs under.− - [Roadmap](https://docs.repowise.dev/roadmap): What we are building next, what we have decided not to build, and why there are no dates on this page.− - [Upgrading](https://docs.repowise.dev/upgrading): Upgrade the repowise package, run repowise update, and your existing index keeps working. No reindex in the normal case; a full reindex is only ever recommended, never forced.− - [Agents: add, remove, refresh](https://docs.repowise.dev/cli/agents): Wire repowise into Claude Code, Codex, Cursor, VS Code, OpenCode, or Hermes, or drop the config snippet for anything else.− - [Decisions: capture, review, govern](https://docs.repowise.dev/cli/decision): Record architectural decisions so the why survives the team. Review what capture proposed, accept the ones that should govern, keep the manifest in git, and control which sources run.− - [Distill: compact command output](https://docs.repowise.dev/cli/distill): Run noisy commands through repowise distill for an errors-first, fully reversible rendering that cuts 60 to 90% of the tokens on tests, builds, git, and searches, with zero error-line loss.− - [Coverage and CI gates: coverage, impacted-tests, doc-drift, security check](https://docs.repowise.dev/cli/gates): Flags for ingesting coverage, gating a change on patch coverage, selecting the tests a change needs, and the doc-drift and security gates.− - [Code health: health, risk](https://docs.repowise.dev/cli/health): repowise health scores every file from deterministic markers across three signals (defect risk, maintainability, performance); repowise risk scores the defect risk of a commit or diff range. Both are zero-LLM and run in seconds.− - [Hooks: auto-sync on commit](https://docs.repowise.dev/cli/hook): Install, check, and remove the post-commit git hook that keeps the repowise wiki current after every commit.− - [Indexing: init, update, reindex](https://docs.repowise.dev/cli/indexing): The three commands that build and maintain repowise's intelligence layers. init parses everything from scratch, update is incremental on each commit, reindex rebuilds the vector store without re-running the LLM.− - [Other commands](https://docs.repowise.dev/cli/other): One-shot utilities: costs, next, overlap, dead-code, security scan, doctor, export, generate-claude-md, telemetry, config hints, login/logout/whoami, publish, augment, delete.− - [CLI overview](https://docs.repowise.dev/cli/overview): All `repowise` commands at a glance.− - [Query: search, ask, context, symbol, why, status](https://docs.repowise.dev/cli/query): Search, ask questions, read symbols, and check sync state from the terminal without involving an editor.− - [Server & watch: serve, watch, mcp](https://docs.repowise.dev/cli/server): Run the repowise API and dashboard, auto-update on file save, or expose the MCP server directly to an editor.− - [Uninstall: remove repowise](https://docs.repowise.dev/cli/uninstall): Remove repowise from this repo, and optionally from this machine, with a full inventory of every path it ever wrote.− - [Workspace: multi-repo commands](https://docs.repowise.dev/cli/workspace): Manage repos in a repowise workspace: list, add, remove, scan, and pick the default.− - [Alerts & notifications](https://docs.repowise.dev/hosted/alerts): HMAC-signed Slack-compatible webhooks, the in-product notification bell, and per-kind email preferences, for security events and engineering signals, designed to never spam.− - [PR review bot](https://docs.repowise.dev/hosted/bot): A GitHub App that posts one useful comment per pull request: a before-you-merge checklist, a change-map diagram, code-health deltas, hotspots, hidden coupling, dead code, change risk, and an optional merge gate. Signals mode uses no model and is free for OSS; AI review is part of Pro.− - [Connecting your IDE](https://docs.repowise.dev/hosted/connecting-ide): Mint an API key on the hosted dashboard and paste a snippet. One URL per indexed repo, plus one per workspace that answers across its member repos. Claude Code, Claude Web/Desktop, Cursor, VS Code, and Windsurf supported.− - [Security and data handling](https://docs.repowise.dev/hosted/data-handling): For a security reviewer evaluating Hosted at repowise.dev. What happens to your source code, what is kept after indexing, when a model sees your code, who can read it, and how data is deleted.− - [Jira and Confluence](https://docs.repowise.dev/hosted/integrations): Connect an Atlassian site to link architectural decisions to the Jira tickets that motivated them, and publish your generated wiki to Confluence on a weekly schedule, updated in place and never duplicated.− - [Hosted platform](https://docs.repowise.dev/hosted/overview): Everything the managed platform adds on top of the OSS engine: zero-ops indexing, push-sync, AI docs and chat, the security suite, team portfolio intelligence, and alerting, with a plan ladder from free to enterprise.− - [Security suite](https://docs.repowise.dev/hosted/security): CVE-aware dependency scanning with usage and reachability triage, secret detection across full git history, SBOM/VEX export, a nightly CVE refresh, compliance reports, and an insert-only audit trail.− - [Teams & portfolio intelligence](https://docs.repowise.dev/hosted/teams): Seats with pooled repos and credits, shared workspaces, portfolio health and ownership rollups, and an engineering-leader dashboard fed by nightly drift detection.− - [Hosted vs self-hosted](https://docs.repowise.dev/hosted/vs-self-hosted): Both modes ship the same intelligence layers, the same MCP tools, and the same dashboard. The differences are about ops, billing, and team features, not about what the agent can do.− - [Configuration: config.yaml & ignore files](https://docs.repowise.dev/installation/configuration): The .repowise/ directory, the config.yaml file repowise generates on first init, and how to control which files get indexed with .gitignore, nested .gitignore, .repowiseIgnore, and --exclude.− - [Environment variables](https://docs.repowise.dev/installation/env-vars): Provider API keys, embedder overrides, and runtime knobs that configure repowise's behavior at install and index time.− - [Language support](https://docs.repowise.dev/installation/languages): 26 languages parsed to a full AST and 40 on the five-rung ladder, with per-language framework awareness for Django, FastAPI, Spring Boot, Rails, Laravel, Godot and more.− - [Requirements](https://docs.repowise.dev/installation/requirements): System and toolchain requirements for self-hosted repowise, covering Python, Git, disk, and an LLM provider key.− - [Troubleshooting](https://docs.repowise.dev/installation/troubleshooting): Diagnose a broken index with repowise doctor, plus the most common install and indexing problems with their fixes.− - [Architecture diagrams](https://docs.repowise.dev/intelligence/architecture-diagrams): The architecture map in your documentation, the C4 system context, container and component views built from the index, and the Structurizr DSL export. All built from the dependency graph and manifests, with no model.− - [Auto-generated wiki](https://docs.repowise.dev/intelligence/auto-wiki): How repowise writes a documentation page for every module and notable file: incrementally, with citations, with confidence scoring, and refreshed in under 30 seconds per commit.+ ## Research+ - [Who Wrote This?](https://repowise.dev/resources/ai-governance): The engineering leader's guide to governing AI-written code, and the technical debt that comes with it+ Who Wrote This? is a free field guide from Repowise for engineering leaders whose teams use coding agents. It measures how AI-era code differs in 200+ popular open-source repositories, compared at the same age, and turns the findings into actions and a maturity model.+ - Popular open-source projects built with coding agents carry about 4.5 times the share of too-big functions that projects started in 2021-22 had at the same age, and about 3 times after accounting for codebase size. (Our study of 200+ open-source repositories, 2026, observational, projects compared at the same age; chapter 2)+ - Commit trailers miss much of the agent use: 34 of 79 young projects that barely credited agents still added an agent config file within two months. (Our study of 200+ open-source repositories, 2026, observational, young projects with few agent credits; chapter 3)+ - In agent-era projects, each contributor adds over three times as much new code a week as in older projects of the same age, and all of it lands on the same reviewers. (Our study of 200+ open-source repositories, 2026, observational, lines added per contributor-week at six months; chapter 4)+ - Splitting a big function moves the work: its new helpers take 41% to 57% of the later edits in that area. (Our study of 200+ open-source repositories, 2026, observational, later edits after a split; chapter 6)+ - In a controlled trial, experienced developers were 19% slower with AI while believing they were faster. (METR randomised trial, 16 developers, 246 issues, early 2025; chapter 1)+ - [AI provenance](https://repowise.dev/features/agent-provenance): Know which commits an agent wrote, with coverage+ - [Architecture & Dependency Graph: The Complete Guide to Diagrams Derived From Code](https://repowise.dev/guides/architecture): How repowise parses your repo into one directed dependency graph across 27 languages, ranks it with centrality, and derives browsable C4 and knowledge-graph views with no LLM in the layout path.+ - [Agent Provenance: Which Commits an Agent Wrote, with Coverage](https://repowise.dev/guides/agent-provenance): How repowise labels commits agent, human-attested or unknown from the evidence a repository carries, and why every AI share is shown with its coverage and withheld below 30 percent.+ - [Auto-sync](https://docs.repowise.dev/auto-sync): Six ways to keep your repowise index current: a post-commit hook, a file watcher, GitHub, GitLab and Gitea or Forgejo webhooks, and a polling safety net.+ - [Build on Repowise](https://docs.repowise.dev/build-on-repowise): The surfaces a tool, service or agent can build on, how each one authenticates, and which contracts are versioned and stable across releases.+ - [Gates in CI](https://docs.repowise.dev/ci): Gate pull requests in CI on patch coverage, new doc drift, new security findings, new code-health findings and change risk, enforce a change policy, and run only the tests needed.+ - [Local dashboard](https://docs.repowise.dev/dashboard): The self-hosted repowise dashboard reads your local index to answer architecture, health, ownership and history questions, with nothing leaving your machine.+ - [Enterprise](https://docs.repowise.dev/enterprise): repowise for platform, AppSec and architecture leads: change and component evidence computed inside your network, and what the commercial licence adds.+ - [Welcome to repowise](https://docs.repowise.dev): repowise indexes your repository into five intelligence layers and serves them to your AI coding agent through MCP tools, so it reads answers, not code.+ - [Licensing](https://docs.repowise.dev/licensing): repowise is AGPL-3.0. What that allows, why internal use creates no obligation to publish your code, and when a company needs a commercial licence.+ - [Roadmap](https://docs.repowise.dev/roadmap): What we are building next across languages, source control beyond git, multi-repo, integrations and core intelligence, plus what we have decided not to build.+ - [Upgrading](https://docs.repowise.dev/upgrading): Upgrade the repowise package, run repowise update, and your existing index keeps working. No reindex in the normal case, and a full reindex is never forced.+ - [Agents: add, remove, refresh](https://docs.repowise.dev/cli/agents): Wire repowise into Claude Code, Codex, Cursor, VS Code, OpenCode, Hermes, GitHub Copilot CLI or Kiro, or drop the config snippet for anything else.+ - [Change evidence: changes, check, suspects, report, events](https://docs.repowise.dev/cli/changes): Change Records rebuilt from git with an evidence checklist, plus repowise check for change policy, suspects for a symptom, evidence reports and events.+ - [Components, packages and attribution](https://docs.repowise.dev/cli/components): Declare Backstage-shaped components with owners checked against recent activity, export package usage as CycloneDX, and read three-state AI attribution.+ - [Decisions: capture, review, govern](https://docs.repowise.dev/cli/decision): Record architectural decisions so the why survives the team. Review the candidates capture proposed, accept the ones that should govern, and keep them in git.+ - [Distill: compact command output](https://docs.repowise.dev/cli/distill): repowise distill renders noisy command output errors-first and fully reversible, saving 61 to 89% of tokens in measured runs on tests, git log and git diff.+ - [Coverage and CI gates: coverage, impacted-tests, doc-drift, security check, health check](https://docs.repowise.dev/cli/gates): Flags for ingesting coverage, gating a change on patch coverage, selecting the tests a change needs, and the doc-drift, security and health gates.+ - [Code health: health, risk](https://docs.repowise.dev/cli/health): repowise health scores every file on defect risk, maintainability and performance; repowise risk ranks a commit or diff range against recent commits.+ - [Hooks: auto-sync on commit](https://docs.repowise.dev/cli/hook): Install, check and remove the post-commit git hook that runs repowise update after every commit, and see hook stats on what your agent hooks fired.+ - [Indexing: init, update, reindex](https://docs.repowise.dev/cli/indexing): repowise init builds the intelligence layers from scratch, update keeps them current on each commit, and reindex rebuilds the vector store with no LLM.+ - [Other commands](https://docs.repowise.dev/cli/other): One-shot repowise utilities including costs, next, overlap, dead-code, security scan, doctor, whats-new, export, telemetry, login, publish and delete.+ - [CLI overview](https://docs.repowise.dev/cli/overview): Every repowise CLI command at a glance, from init, update and serve to search, health, risk, distill and decision, with a link to each command's full guide.+ - [Query: search, ask, context, symbol, why, status](https://docs.repowise.dev/cli/query): Search the docs, ask cited questions, read triage cards and symbols, trace why code exists, and check sync state from the terminal with repowise search.+ - [Server & watch: serve, watch, mcp](https://docs.repowise.dev/cli/server): Run repowise serve for the API and local dashboard, repowise watch to auto-update on file save, or repowise mcp to expose the MCP server to your editor.+ - [Uninstall: remove repowise](https://docs.repowise.dev/cli/uninstall): Remove repowise from this repo, and optionally from this machine, with a full inventory of every path it wrote and a report of what was removed and kept.+ - [Workspace: multi-repo commands](https://docs.repowise.dev/cli/workspace): Manage repos in a repowise workspace: list, add, remove, scan, set the default, explain contract links, lint architecture rules and read architecture metrics.+ - [Set up with your agent](https://docs.repowise.dev/getting-started/for-agents): Paste one line into Claude Code, Codex, Cursor or any coding agent and it installs repowise, indexes the repo, connects the MCP tools and asks one question.+ - [How it works](https://docs.repowise.dev/getting-started/how-it-works): How repowise builds its index in five passes (dependency graph, git history, wiki, decision records and code health) and how the MCP tools query the result.+ - [Agent plugins](https://docs.repowise.dev/getting-started/plugins): The Claude Code and Codex plugins bundle the repowise MCP server, lifecycle hooks, skills and slash commands into one install. See what each ships.+ - [Quickstart](https://docs.repowise.dev/getting-started/quickstart): Install repowise, index your repo with no API key, open the dashboard and connect your agent. Self-hosted, hosted (repowise.dev), or a multi-repo workspace.+ - [Agent setup runbook](https://docs.repowise.dev/getting-started/setup): The step-by-step runbook a coding agent follows to install repowise, index the current repository, connect the MCP tools and report back, readable by anyone.

Showing the first 40 of each.

https://www.repowise.dev/llms.txt

− - [Change risk](https://repowise.dev/features/change-risk): Score any diff before it merges− - [Set up with your agent](https://docs.repowise.dev/getting-started/for-agents): Paste one line into Claude Code, Codex, Cursor, or any coding agent and it installs Repowise, indexes the repo, connects the MCP tools, and asks you one question. Also covers the Claude Code plugin, per-host setup, and the Markdown endpoints agents read.− - [How it works](https://docs.repowise.dev/getting-started/how-it-works): The five intelligence layers Repowise computes and how they fit together.− - [Agent plugins](https://docs.repowise.dev/getting-started/plugins): The Claude Code and Codex plugins bundle the MCP server, lifecycle hooks, skills, and slash commands into one install. What each plugin ships, how to install it, and what activates when.− - [Quickstart](https://docs.repowise.dev/getting-started/quickstart): Install repowise, index your repo, and connect Claude Code in under a minute. Two paths, self-hosted (pip) or hosted (repowise.dev).− - [Agent setup runbook](https://docs.repowise.dev/getting-started/setup): Step-by-step instructions a coding agent follows to install Repowise, index the current repository, connect the MCP tools, and report back. Written for the agent, readable by anyone.− - [VS Code extension](https://docs.repowise.dev/getting-started/vscode): The Repowise extension brings the local index into VS Code (editor-native health signals, refactoring CodeLens, branch risk, in-editor dashboards) and registers the Repowise MCP server so the same index serves both you and your AI agent.− - [What is repowise](https://docs.repowise.dev/getting-started/what-is-repowise): Repowise indexes your codebase into five intelligence layers (graph, git, wiki, decisions, code health) and exposes them to AI agents through task-shaped MCP tools. The why your AI agent has been missing.− - [AI Code Review Pricing Compared: CodeRabbit, Greptile, Qodo, Copilot and repowise per 100 PRs](https://repowise.dev/blog/comparisons/ai-code-review-pricing-compared): What CodeRabbit, Greptile, Qodo, GitHub Copilot and repowise cost per 100 pull requests for teams of 5, 25 and 100 developers, from October 2026 prices.− - [Augment Code Alternatives: Context Engine Options for Claude Code, Cursor and Codex](https://repowise.dev/blog/comparisons/augment-context-engine-alternatives): Seven alternatives to Augment's Context Engine MCP, from free local code graphs to hosted indexes, compared on price, license, private repos and freshness.− - [CodeSee Alternatives: Codebase Map and Visualizer Tools for 2026](https://repowise.dev/blog/comparisons/codesee-alternatives-codebase-maps): Learn what happened to CodeSee after GitKraken bought it, and compare six codebase map tools that cover its maps, review maps and dependency views in 2026.− - [DeepWiki for Private Repos: Your Options in 2026](https://repowise.dev/blog/comparisons/deepwiki-private-repos): DeepWiki is free for public repos only. We compare what each private-repo route costs, where your code goes and how fresh the pages stay.− - [Serena vs Graphify vs CodeGraph vs repowise: Benchmarked on the Same Repos](https://repowise.dev/blog/comparisons/serena-vs-graphify-vs-codegraph-vs-repowise): Four open-source code context tools for coding agents, run on the same questions: tokens, tool calls, retrieval, call-graph accuracy and index time.− - [SonarQube Alternatives 2026: Open Source and for Small Teams](https://repowise.dev/blog/comparisons/sonarqube-alternatives): Eight SonarQube alternatives compared on licence, self-hosting, free tier, price and setup effort, split by job: rules, security, code health and history.− - [Sourcegraph Alternatives 2026: Open Source, Self-Hosted and AI Context](https://repowise.dev/blog/comparisons/sourcegraph-alternatives-2026): Sourcegraph is now enterprise-only from $16K a year. The alternatives, split by job: code search, context for coding agents, and understanding code.− - [Sourcegraph vs GitHub Code Search vs Rolling Your Own: A Build-vs-Buy Cost Table](https://repowise.dev/blog/comparisons/sourcegraph-vs-github-code-search-vs-build-your-own): See what GitHub code search covers for free, what Sourcegraph adds from $16K a year, and what a zoekt or embeddings stack costs in engineer-hours.− - [Structurizr vs Mermaid vs PlantUML for C4 (and When to Generate Instead)](https://repowise.dev/blog/comparisons/structurizr-vs-mermaid-vs-plantuml-c4): The same C4 container diagram written in Structurizr DSL, Mermaid and C4-PlantUML, with a feature table and an honest look at how fast each one goes stale.− - [Technical Debt Measurement Tools Compared: What Each One Measures, and Whether It Predicts Bugs](https://repowise.dev/blog/comparisons/technical-debt-measurement-tools-compared): SonarQube, CodeScene, Qlty, Codacy, NDepend and repowise compared on what their technical debt score measures and what evidence links it to bugs.− - [LLM Code Review Tools: CodeRabbit, Greptile, Qodo, Sourcery and the Deterministic Layer](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): LLM code review tools compared on price, noise and repo context: CodeRabbit, Greptile, Qodo, Sourcery, PR-Agent, plus when to add a deterministic layer.− - [Best Architecture Documentation Tools (C4, Diagrams, Decisions)](https://repowise.dev/blog/comparisons/best-architecture-documentation-tools): Compare Structurizr, IcePanel, Mermaid, PlantUML and repowise for C4 diagrams and architecture decision records, and see which keeps docs in step with the code.− - [Best Code Health Tools in 2026](https://repowise.dev/blog/comparisons/best-code-health-tools-2026): Best code health tools in 2026 are the ones that measure more than static warnings. They show where change is concentrated, where complexity is rising, where…− - [Best Code Search Tools for Engineering Teams](https://repowise.dev/blog/comparisons/best-code-search-tools-teams): Compare Sourcegraph, Greptile, GitHub code search, Zoekt and repowise on exact, symbol and semantic search, self-hosting and index freshness at team scale.− - [Best Codebase Documentation Tools for AI Coding Agents](https://repowise.dev/blog/comparisons/best-codebase-documentation-tools-ai-agents): Compare repowise, DeepWiki, Mintlify, Cursor indexing and Greptile on what coding agents need from docs: MCP access, freshness, self-hosting and repo context.− - [Code Visualization Tools Compared: Graphs, Maps and Diagrams](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): Code visualization tools compared: repowise, Structurizr, GitDiagram, Madge, dependency-cruiser and what replaced CodeSee, with what each one draws.− - [Dead Code Analysis: The Best Detection Tools by Language (2026)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Dead code analysis tools by language: Vulture and deadcode for Python, Knip for TypeScript, Go deadcode, Java inspections, and unused dependency checkers.− - [Best Dependency Graph Tools for Monorepos](https://repowise.dev/blog/comparisons/best-dependency-graph-tools-monorepos): Compare Nx Graph, Turborepo, Madge, Dependency-Cruiser and repowise on package and symbol-level edges, circular dependency detection and change impact.− - [Git Analytics Tools: Code-Level and Team-Level, Compared](https://repowise.dev/blog/comparisons/best-git-analytics-tools): Git analytics tools compared: CodeScene, repowise and GitClear for hotspots and ownership, LinearB, Swarmia and Jellyfish for team metrics, with prices.− - [PR Review Bots for GitHub: 6 Compared With Pricing (2026)](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): PR review bots for GitHub compared on price, noise and context: CodeRabbit, Greptile, Copilot code review, Codacy, Reviewdog and the repowise bot.− - [Best MCP Servers for Coding Agents](https://repowise.dev/blog/comparisons/best-mcp-servers-coding-agents): best mcp servers for coding agents only matter if they answer a hard question: which server gives an agent the right context with the fewest extra tool…− - [Best Open Source Alternatives to CodeScene](https://repowise.dev/blog/comparisons/best-open-source-codescene-alternatives): codescene open source alternatives are a good fit if you want hotspot analysis, ownership signals, and dependency insight without a per-author bill.…− - [Best Refactoring Tools and Prioritization Platforms](https://repowise.dev/blog/comparisons/best-refactoring-tools): Best refactoring tools are the ones that tell you what to fix first, not just what looks messy. A codebase full of lint warnings is easy to generate and hard…− - [Best Self-Hosted Codebase Documentation Platforms](https://repowise.dev/blog/comparisons/best-self-hosted-codebase-documentation): Best self hosted documentation starts with a simple constraint: your docs have to live where your code lives, and your editors, search, identity, and…− - [Static Analysis Tools for Large Codebases (2026): Open Source and Commercial](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): Static analysis tools compared: SonarQube, Semgrep, CodeQL, Coverity, and the best open-source analyzers for Python, JS/TS, Java, Go, C/C++ and C#.− - [Best Tools for Test Coverage Analysis (Per-File and Trend)](https://repowise.dev/blog/comparisons/best-test-coverage-tools): best test coverage tools do more than print a single percentage. They tell you which files are drifting, which lines stay dark, and which parts of the…− - [Best Tools for Engineering Managers to See Codebase Risk](https://repowise.dev/blog/comparisons/best-tools-engineering-managers-codebase-risk): Engineering manager codebase tools are only useful if they answer three questions fast: where is risk concentrated, who owns it, and what breaks if one…− - [Engineering Onboarding Tools: The Best Tools to Onboard New Engineers (2026)](https://repowise.dev/blog/comparisons/best-tools-for-onboarding-engineers): Engineering onboarding tools compared: repowise, Swimm, CodeTour, Confluence or Notion, and Stack Internal, with a stack and a scorecard by team size.− - [Best Tools to Generate CLAUDE.md / AGENTS.md Files](https://repowise.dev/blog/comparisons/best-tools-generate-claude-md-agents-md): The best claude.md generators are the ones that produce useful, repo-specific guidance instead of a wall of generic prose. A good CLAUDE.md or AGENTS.md…− - [Best Tools to Understand a Legacy Codebase Fast](https://repowise.dev/blog/comparisons/best-tools-understand-legacy-codebase): A good understand legacy codebase workflow does not start with editing. It starts with reducing unknowns. On day one, the cost is not syntax. It is context:…− - [5 Best Codebase Documentation Tools in 2026 (Compared)](https://repowise.dev/blog/comparisons/best-codebase-documentation-tools-2026): Compare repowise, DeepWiki, CodeScene, Sourcegraph and Google CodeWiki on generated docs, self-hosting, git intelligence and MCP support for coding agents.− - [repowise vs CodeScene: Full Codebase Intelligence Without the Enterprise Price Tag](https://repowise.dev/blog/comparisons/repowise-vs-codescene): CodeScene pioneered hotspot analysis but stops at a dashboard. repowise gives you the same git intelligence open-source, self-hosted, and queryable by AI agents.+ - [Change risk](https://repowise.dev/features/change-risk): See what a change reaches before it merges+ - [Set up with your agent](https://docs.repowise.dev/getting-started/for-agents): Paste one line into Claude Code, Codex, Cursor, or any coding agent and it installs Repowise, indexes the repo, connects the MCP tools, and asks you one question. Also covers the Claude Code plugin, per-host setup, and the Markdown endpoints agents read.+ - [How it works](https://docs.repowise.dev/getting-started/how-it-works): The five intelligence layers Repowise computes and how they fit together.+ - [Agent plugins](https://docs.repowise.dev/getting-started/plugins): The Claude Code and Codex plugins bundle the MCP server, lifecycle hooks, skills, and slash commands into one install. What each plugin ships, how to install it, and what activates when.+ - [Quickstart](https://docs.repowise.dev/getting-started/quickstart): Install repowise, index your repo, and connect Claude Code in under a minute. Two paths, self-hosted (pip) or hosted (repowise.dev).+ - [Agent setup runbook](https://docs.repowise.dev/getting-started/setup): Step-by-step instructions a coding agent follows to install Repowise, index the current repository, connect the MCP tools, and report back. Written for the agent, readable by anyone.+ - [VS Code extension](https://docs.repowise.dev/getting-started/vscode): The Repowise extension brings the local index into VS Code (editor-native health signals, refactoring CodeLens, branch risk, in-editor dashboards) and registers the Repowise MCP server so the same index serves both you and your AI agent.+ - [What is repowise](https://docs.repowise.dev/getting-started/what-is-repowise): Repowise indexes your codebase into five intelligence layers (graph, git, wiki, decisions, code health) and exposes them to AI agents through task-shaped MCP tools. The why your AI agent has been missing.+ - [AI Code Review on GitLab Merge Requests: 2026 Guide](https://repowise.dev/blog/comparisons/ai-code-review-gitlab-merge-requests): AI code review on GitLab merge requests in 2026: GitLab Duo, CodeRabbit, Qodo, Greptile and open-source CI options, with setup, self-managed support, pricing.+ - [Claude Code Review Pricing: What It Costs per PR, and a Tiered Budget for 200 Pull Requests](https://repowise.dev/blog/comparisons/claude-code-review-pricing): Claude Code Review averages $15 to $25 per pull request on Anthropic's docs. See how it is billed, what drives cost, and a tiered monthly budget for 200 PRs.+ - [CodeRabbit Pricing in 2026: Plans, Seats, Limits and Usage Billing Explained](https://repowise.dev/blog/comparisons/coderabbit-pricing): CodeRabbit costs $24 to $72 per developer a month billed annually. Plans, who counts as a seat, hourly limits and $0.25 per file overage for 5, 25 and 100 devs.+ - [Cursor Bugbot Pricing in 2026: What a Run Costs, and Alternatives](https://repowise.dev/blog/comparisons/cursor-bugbot-pricing-alternatives): Cursor Bugbot is usage-based since May 2026, about $1.00 to $1.50 per run. What 50, 250 and 1,000 PRs cost, and how it compares with CodeRabbit and Greptile.+ - [Free AI Code Review for Open Source: Every Free Option for Maintainers in 2026](https://repowise.dev/blog/comparisons/free-ai-code-review-open-source): Every free AI code review option for open-source repos in 2026: CodeRabbit, Qodo, Greptile, Bito, Copilot, PR-Agent, reviewdog and repowise, with limits.+ - [GitHub Copilot Code Review Cost: AI Credits, Actions Minutes and a 25-Developer Estimate](https://repowise.dev/blog/comparisons/github-copilot-code-review-cost): What Copilot code review costs since 1 June 2026: AI Credits per review, Actions minutes on private repos, seat prices, a 25-dev estimate and alternatives.+ - [Greptile Pricing in 2026: Credits, Base vs Plus vs Apex, and What a Month Costs](https://repowise.dev/blog/comparisons/greptile-pricing): Greptile Pro is $30 a seat with 50 credits and $1 per extra credit. Base, Plus and Apex cost 1, 3 and 10 credits per review. Worked bills by team size.+ - [AI Code Review Pricing Compared: repowise, CodeRabbit, Greptile, Qodo and Copilot per 100 PRs](https://repowise.dev/blog/comparisons/ai-code-review-pricing-compared): What repowise, CodeRabbit, Greptile, Qodo and GitHub Copilot cost per 100 pull requests for teams of 5, 25 and 100 developers, from October 2026 prices.+ - [Augment Context Engine Alternatives for Claude Code, Cursor and Codex](https://repowise.dev/blog/comparisons/augment-context-engine-alternatives): Augment's Context Engine is an MCP server billed per query. Compare CodeGraph, Graphify, Serena, GitNexus, Sourcegraph, Greptile and repowise on price, license and reach.+ - [CodeSee Alternatives: Codebase Map and Visualizer Tools for 2026](https://repowise.dev/blog/comparisons/codesee-alternatives-codebase-maps): CodeSee's public site no longer loads after GitKraken bought it. Compare six tools that replace its codebase maps, PR review maps and dependency graphs.+ - [DeepWiki for Private Repos: Your Options in 2026](https://repowise.dev/blog/comparisons/deepwiki-private-repos): DeepWiki for private repos runs through a Devin account. We compare it with self-hosted and hosted routes on cost, data handling and freshness.+ - [Serena vs Graphify vs CodeGraph vs repowise: Benchmarked on the Same Repos](https://repowise.dev/blog/comparisons/serena-vs-graphify-vs-codegraph-vs-repowise): Serena, Graphify, CodeGraph and repowise compared on the same repos: agent tokens, file retrieval, call-graph accuracy, index time and which to pick.+ - [SonarQube Alternatives in 2026: Open Source and Small-Team Options](https://repowise.dev/blog/comparisons/sonarqube-alternatives): Eight SonarQube alternatives compared on licence, free tier, price and what each one checks, from Semgrep and Opengrep to Codacy, CodeScene and repowise.+ - [Sourcegraph Alternatives 2026: Open Source, Self-Hosted and AI Context](https://repowise.dev/blog/comparisons/sourcegraph-alternatives-2026): Sourcegraph now lists only an Enterprise plan from $16K a year. Eight alternatives, split by the job: exact code search, agent context, and understanding code.+ - [Sourcegraph vs GitHub Code Search vs Rolling Your Own: A Build-vs-Buy Cost Table](https://repowise.dev/blog/comparisons/sourcegraph-vs-github-code-search-vs-build-your-own): GitHub code search is free, Sourcegraph starts at $16K a year, and a zoekt or embeddings stack costs 70 to 500 engineer-hours. Pick by repos, hosts and branches.+ - [Structurizr vs Mermaid vs PlantUML for C4 (and When to Generate Instead)](https://repowise.dev/blog/comparisons/structurizr-vs-mermaid-vs-plantuml-c4): The same C4 container diagram written in Structurizr DSL, Mermaid and C4-PlantUML, with a feature table and a look at how each one keeps up with the code.+ - [Technical Debt Measurement Tools Compared: What Each Score Measures](https://repowise.dev/blog/comparisons/technical-debt-measurement-tools-compared): SonarQube, CodeScene, Qlty, Codacy, NDepend and repowise compared on what their technical debt score counts, and which have evidence it points at bugs.+ - [Best AI Code Review Tools in 2026: Nine Tools Compared](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): CodeRabbit is the broadest AI code reviewer, Greptile the deepest on repo context and PR-Agent the one you self-host. Nine tools compared on price and fit.+ - [Best Architecture Documentation Tools in 2026: C4, ADRs and Diagrams](https://repowise.dev/blog/comparisons/best-architecture-documentation-tools): Structurizr, IcePanel, Mermaid, PlantUML, Eraser, Backstage TechDocs, Log4brains and repowise compared on C4 views, ADRs and keeping docs current with the code.+ - [Best Code Health Tools in 2026: Five Compared](https://repowise.dev/blog/comparisons/best-code-health-tools-2026): CodeScene leads on hotspot analysis, SonarQube on quality gates and Codacy on PR checks. Five code health tools compared on pricing, scoring and fit.+ - [Best Code Search Tools for Engineering Teams in 2026](https://repowise.dev/blog/comparisons/best-code-search-tools-teams): Sourcegraph, GitHub code search, Zoekt, OpenGrok, Greptile and repowise compared on exact, symbol and semantic search, self-hosting, price and agent access.+ - [Best Codebase Documentation Tools for AI Coding Agents (2026)](https://repowise.dev/blog/comparisons/best-codebase-documentation-tools-ai-agents): repowise, DeepWiki, Google Code Wiki, Mintlify, Context7, Cursor and Greptile compared on what coding agents need: MCP access, freshness, private repos.+ - [Best Code Visualization Tools in 2026: Graphs, Maps and Diagrams](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): Best code visualization tools in 2026: repowise, Structurizr, CodeScene, GitDiagram, Madge and dependency-cruiser compared on what each draws and how current it stays.+ - [Best Dead Code Detection Tools by Language (2026)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Knip for JavaScript and TypeScript, Vulture for Python, deadcode for Go, and repowise for mixed-language repos: dead code tools compared, with a safe way to delete.+ - [Best Dependency Graph Tools for Monorepos in 2026](https://repowise.dev/blog/comparisons/best-dependency-graph-tools-monorepos): Nx, Turborepo, Madge, dependency-cruiser, Knip and repowise compared on package and file-level graphs, circular dependencies and change impact.+ - [Git Analytics Tools: Code-Level and Team-Level, Compared](https://repowise.dev/blog/comparisons/best-git-analytics-tools): CodeScene and repowise lead on hotspots, ownership and bus factor; Swarmia and LinearB on team metrics. Six git analytics tools compared with prices.+ - [Best GitHub PR Review Bots in 2026: 6 Compared With Pricing](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): The best GitHub PR review bots in 2026 compared on price, noise and context: CodeRabbit, Greptile, Copilot code review, Codacy, Reviewdog and repowise.+ - [Best MCP Servers for Coding Agents in 2026](https://repowise.dev/blog/comparisons/best-mcp-servers-coding-agents): The best MCP servers for coding agents: repowise for codebase context, Context7 for docs, GitHub for PRs, Playwright for browsers, with a stack by use case.+ - [Best Open Source Alternatives to CodeScene in 2026](https://repowise.dev/blog/comparisons/best-open-source-codescene-alternatives): repowise, code-maat, PyDriller and SonarQube Community Build compared as open source CodeScene alternatives for hotspots, ownership and code health.+ - [Best Refactoring Tools in 2026: What to Fix First and How](https://repowise.dev/blog/comparisons/best-refactoring-tools): The best refactoring tools rank what to fix first, then help you change it safely. CodeScene, SonarQube, CAST Imaging, Moderne, JetBrains IDEs and repowise compared.+ - [Best Self-Hosted Codebase Documentation Tools in 2026](https://repowise.dev/blog/comparisons/best-self-hosted-codebase-documentation): Compare repowise, Backstage TechDocs, BookStack, Outline, Docusaurus and GitBook for self-hosted codebase documentation, with licenses, auth and pricing.+ - [Best Static Analysis Tools for Large Codebases in 2026](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): SonarQube, Semgrep, CodeQL and Coverity compared for large codebases, plus the free analyzer to run per language and the context layer that ties findings together.

Showing the first 40 of each.

https://www.repowise.dev/llms.txt

− - [repowise vs SonarQube](https://repowise.dev/compare/sonarqube-alternative): SonarQube is the stronger fit when CI enforcement, rules, and quality gates are the contract. Repowise is built for repository understanding and prioritization, not as a drop-in replacement for every Sonar rule or gate.− - [repowise vs Snyk Code](https://repowise.dev/compare/snyk-code-alternative): Snyk Code is the appropriate choice when source-code security scanning and remediation are the buying requirement. Repowise covers a wider intelligence surface but should not be represented as a replacement for a dedicated SAST program.− - [repowise vs Code Climate / Qlty](https://repowise.dev/compare/codeclimate-qlty-alternative): Qlty is the direct path for teams seeking the current Code Climate lineage of maintainability and coverage workflows. Repowise adds architecture, history, decisions, documentation, and agent retrieval around code-health evidence.− - [repowise vs CodeRabbit](https://repowise.dev/compare/coderabbit-alternative): CodeRabbit is the direct fit for automated review comments and review assistance. Repowise focuses on durable context, health, architecture, history, decisions, and documentation instead of acting as the review voice itself.− - [Other commands](https://docs.repowise.dev/cli/other): One-shot utilities: costs, next, overlap, dead-code, security scan, doctor, export, generate-claude-md, telemetry, login/logout/whoami, augment, delete.− - [Architecture metrics](https://docs.repowise.dev/multi-repo/architecture-metrics): The one evaluative read of the whole system, propagation cost, the cyclic core, per-service roles, and a deterministic 1-10 architecture score. Standard architecture-complexity metrics computed over the system graph, no LLM.− - [Cross-repo blast radius](https://docs.repowise.dev/multi-repo/blast-radius): If you change this service, what downstream services and repos break? Blast radius walks the system graph against its edges and returns every reachable service ranked by impact.− - [Breaking-change guard](https://docs.repowise.dev/multi-repo/breaking-changes): Did a provider change in a way that actually breaks its consumers? On every workspace update, freshly-extracted contracts are diffed against the previous index and each incompatible change is reported with the exact consumer files it endangers.− - [Architecture conformance](https://docs.repowise.dev/multi-repo/conformance): Declare which services may depend on which others, then continuously check the live system graph against those rules. Your team's architecture lint, plus automatic dependency-cycle detection.− - [Cross-repo intelligence](https://docs.repowise.dev/multi-repo/cross-repo): What repowise learns from analyzing several repos together. Co-change pairs, API contracts (HTTP / gRPC / topics), and package dependency mapping. Hidden coupling that single-repo tools can't find.− - [System graph & map](https://docs.repowise.dev/multi-repo/system-map): The service-granular system graph repowise folds every cross-repo signal into, the System Map that renders it, and the extraction diagnostics that explain why a contract link did or didn't form.− - [Workspace MCP mode](https://docs.repowise.dev/multi-repo/workspace-mcp): Self-hosted workspace mode. Pass repo="backend" to target one workspace repo, or repo="all" on the four tools that federate, plus three workspace-only tools for cross-repo blast radius, conformance, and architecture.− - [Workspace setup](https://docs.repowise.dev/multi-repo/workspace-setup): Index multiple related git repos as a single repowise workspace. Get cross-repo co-changes, API contract matching, and MCP queries that federate across member repos on the tools that support it, on top of per-repo intelligence.− - [Best AI Code Review Tools (LLM-Based and Deterministic)](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): Best AI code review tools fall into two camps: LLM-based reviewers that try to reason about intent, architecture, and change impact, and deterministic…− - [Best Codebase Visualization Tools (Graphs, Maps, Diagrams)](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): A hands-on comparison of Structurizr, CodeSee, Sourcetrail, Madge and repowise for dependency graphs, C4 diagrams and code maps you can act on.− - [Best Dead Code Detection Tools (Open Source and Commercial)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Compare repowise, Knip, ts-prune, Vulture and IDE inspections on unused files, unused exports and unused packages, and a cleanup playbook that keeps false positives down.− - [Best Git Analytics Tools (Hotspots, Ownership, Bus Factor)](https://repowise.dev/blog/comparisons/best-git-analytics-tools): Best git analytics tools are the ones that answer three concrete questions fast: where is change concentrated, who understands it, and what breaks if that…− - [Best GitHub PR Review Bots in 2026](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): Compare CodeRabbit, Greptile, Codacy, Reviewdog and the repowise PR bot on review quality, comment noise, repo context, self-hosting and pricing shape.− - [Best Static Analysis Tools for Large Codebases](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): Compare SonarQube, Semgrep, CodeQL, Coverity and repowise on cross-file analysis, false-positive noise and language coverage in large, long-lived codebases.− - [Best Tools for Onboarding New Engineers (2026)](https://repowise.dev/blog/comparisons/best-tools-for-onboarding-engineers): Best onboarding tools for engineers are the ones that shorten the time between “I cloned the repo” and “I changed the right file for the right reason.” The…− - [repowise vs Google CodeWiki: Why Open Source Wins for Private Codebases](https://repowise.dev/blog/comparisons/repowise-vs-google-codewiki): Every software engineer has experienced the 'onboarding wall.' You join a new team, clone a massive monorepo, and spend the first three weeks essentially pla...− - [repowise vs Sourcegraph: Documentation + Intelligence, Not Just Search](https://repowise.dev/blog/comparisons/repowise-vs-sourcegraph): For over a decade, Sourcegraph has been the 'Google for code.' In an era where microservices proliferated and codebases exploded in size, Sourcegraph solved ...− - [Code Health: The Complete Guide (2026)](https://repowise.dev/blog/guides/code-health-complete-guide): Code health is a defect-validated measure of how risky code is to change, scored from 53 deterministic markers across three pillars. Reproduce it on your repo.− - [How to Auto-Generate Documentation for Your Codebase with AI](https://repowise.dev/blog/guides/auto-generate-codebase-documentation-ai): Every engineering team starts with a noble intention: 'We will document everything.' It begins with a clean README, a few architecture diagrams in Excalidraw...− 3,878 public repositories are indexed and browsable. Each repository serves the same seven pages: /overview (health, hotspots, structure), /architecture (dependency graph and layered C4 view), /code-health (code health, hotspots, coverage, dead code), /docs (generated documentation), /commits (per-commit change risk), /owners (ownership and bus factor), and /decisions (architectural decision records mined from history). Append the path to any repository URL.+ - [Claude Code](https://repowise.dev/claude-code): Lens, the part of the Claude Code plugin that shows what Claude reads and edits, from a local index+ - [repowise vs SonarQube](https://repowise.dev/compare/sonarqube-alternative): SonarQube is the stronger fit when CI enforcement, rules, and quality gates are the contract. Repowise is built to explain a repository and rank its files for attention, and it does not replace every Sonar rule or gate.+ - [repowise vs Snyk Code](https://repowise.dev/compare/snyk-code-alternative): Snyk Code is the appropriate choice when source-code security scanning and remediation are the buying requirement. Repowise covers code health, git history and architecture, and it does not replace a dedicated SAST program.+ - [repowise vs Code Climate / Qlty](https://repowise.dev/compare/codeclimate-qlty-alternative): Qlty is the direct successor for teams that used Code Climate for maintainability and coverage. Repowise adds architecture, git history, recorded decisions and agent access around its code-health findings.+ - [repowise vs CodeRabbit](https://repowise.dev/compare/coderabbit-alternative): CodeRabbit is the direct fit for line-by-line AI review comments on every pull request. Repowise's PR bot scores change risk from the diff, the dependency graph and git history, and the same index serves documentation, health and agent context outside the review.+ - [Other commands](https://docs.repowise.dev/cli/other): One-shot utilities: costs, next, overlap, dead-code, security scan, doctor, export, generate-claude-md, telemetry, config hints, login/logout/whoami, publish, augment, delete.+ - [Architecture metrics](https://docs.repowise.dev/multi-repo/architecture-metrics): The one evaluative read of the whole system, propagation cost, the cyclic core, per-service roles, and a deterministic 1-10 architecture score. Standard architecture-complexity metrics computed over the system graph, no LLM.+ - [Cross-repo blast radius](https://docs.repowise.dev/multi-repo/blast-radius): If you change this service, what downstream services and repos break? Blast radius walks the system graph against its edges and returns every reachable service ranked by impact.+ - [Breaking-change guard](https://docs.repowise.dev/multi-repo/breaking-changes): Did a provider change in a way that actually breaks its consumers? On every workspace update, freshly-extracted contracts are diffed against the previous index and each incompatible change is reported with the exact consumer files it endangers.+ - [Architecture conformance](https://docs.repowise.dev/multi-repo/conformance): Declare which services may depend on which others, then continuously check the live system graph against those rules. Your team's architecture lint, plus automatic dependency-cycle detection.+ - [Cross-repo intelligence](https://docs.repowise.dev/multi-repo/cross-repo): What repowise learns from analyzing several repos together. Co-change pairs, API contracts (HTTP / gRPC / topics), and package dependency mapping. Hidden coupling that single-repo tools can't find.+ - [System graph & map](https://docs.repowise.dev/multi-repo/system-map): The service-granular system graph repowise folds every cross-repo signal into, the System Map that renders it, and the extraction diagnostics that explain why a contract link did or didn't form.+ - [Workspace MCP mode](https://docs.repowise.dev/multi-repo/workspace-mcp): Self-hosted workspace mode. Pass repo="backend" to target one workspace repo, or repo="all" on the four tools that federate, plus three workspace-only tools for cross-repo blast radius, conformance, and architecture.+ - [Workspace setup](https://docs.repowise.dev/multi-repo/workspace-setup): Index multiple related git repos as a single repowise workspace. Get cross-repo co-changes, API contract matching, and MCP queries that federate across member repos on the tools that support it, on top of per-repo intelligence.+ - [AI Code Review Pricing Compared: CodeRabbit, Greptile, Qodo, Copilot and repowise per 100 PRs](https://repowise.dev/blog/comparisons/ai-code-review-pricing-compared): What CodeRabbit, Greptile, Qodo, GitHub Copilot and repowise cost per 100 pull requests for teams of 5, 25 and 100 developers, from October 2026 prices.+ - [Augment Code Alternatives: Context Engine Options for Claude Code, Cursor and Codex](https://repowise.dev/blog/comparisons/augment-context-engine-alternatives): Seven alternatives to Augment's Context Engine MCP, from free local code graphs to hosted indexes, compared on price, license, private repos and freshness.+ - [CodeScene Pricing 2026: What a 10, 50 or 200-Dev Team Pays (and Cheaper Options)](https://repowise.dev/blog/comparisons/codescene-pricing): CodeScene charges €18 or €27 per active author a month. Worked yearly costs for 10, 50 and 200 developers, what counts as an author, and cheaper options.+ - [CodeSee Alternatives: Codebase Map and Visualizer Tools for 2026](https://repowise.dev/blog/comparisons/codesee-alternatives-codebase-maps): Learn what happened to CodeSee after GitKraken bought it, and compare six codebase map tools that cover its maps, review maps and dependency views in 2026.+ - [DeepWiki Alternatives 2026: OpenWiki, Google Code Wiki, DeepWiki-Open, repowise](https://repowise.dev/blog/comparisons/deepwiki-alternatives): Five DeepWiki alternatives compared on the same three repos: how far behind HEAD each wiki was, self-hosting, private repo support and agent access.+ - [DeepWiki for Private Repos: Your Options in 2026](https://repowise.dev/blog/comparisons/deepwiki-private-repos): DeepWiki is free for public repos only. We compare what each private-repo route costs, where your code goes and how fresh the pages stay.+ - [IcePanel Alternatives (Including Open Source) for C4 in 2026](https://repowise.dev/blog/comparisons/icepanel-alternatives): Compare seven IcePanel alternatives for C4 diagrams, from open source Structurizr and LikeC4 to Ilograph and C4 generated from code, with prices.+ - [Serena vs Graphify vs CodeGraph vs repowise: Benchmarked on the Same Repos](https://repowise.dev/blog/comparisons/serena-vs-graphify-vs-codegraph-vs-repowise): Four open-source code context tools for coding agents, run on the same questions: tokens, tool calls, retrieval, call-graph accuracy and index time.+ - [SonarQube Alternatives 2026: Open Source and for Small Teams](https://repowise.dev/blog/comparisons/sonarqube-alternatives): Eight SonarQube alternatives compared on licence, self-hosting, free tier, price and setup effort, split by job: rules, security, code health and history.+ - [Sourcegraph Alternatives 2026: Open Source, Self-Hosted and AI Context](https://repowise.dev/blog/comparisons/sourcegraph-alternatives-2026): Sourcegraph is now enterprise-only from $16K a year. The alternatives, split by job: code search, context for coding agents, and understanding code.+ - [Sourcegraph vs GitHub Code Search vs Rolling Your Own: A Build-vs-Buy Cost Table](https://repowise.dev/blog/comparisons/sourcegraph-vs-github-code-search-vs-build-your-own): See what GitHub code search covers for free, what Sourcegraph adds from $16K a year, and what a zoekt or embeddings stack costs in engineer-hours.+ - [Structurizr vs Mermaid vs PlantUML for C4 (and When to Generate Instead)](https://repowise.dev/blog/comparisons/structurizr-vs-mermaid-vs-plantuml-c4): The same C4 container diagram written in Structurizr DSL, Mermaid and C4-PlantUML, with a feature table and an honest look at how fast each one goes stale.+ - [Technical Debt Measurement Tools Compared: What Each One Measures, and Whether It Predicts Bugs](https://repowise.dev/blog/comparisons/technical-debt-measurement-tools-compared): SonarQube, CodeScene, Qlty, Codacy, NDepend and repowise compared on what their technical debt score measures and what evidence links it to bugs.+ - [LLM Code Review Tools: CodeRabbit, Greptile, Qodo, Sourcery and the Deterministic Layer](https://repowise.dev/blog/comparisons/best-ai-code-review-tools): LLM code review tools compared on price, noise and repo context: CodeRabbit, Greptile, Qodo, Sourcery, PR-Agent, plus when to add a deterministic layer.+ - [Code Visualization Tools Compared: Graphs, Maps and Diagrams](https://repowise.dev/blog/comparisons/best-codebase-visualization-tools): Code visualization tools compared: repowise, Structurizr, GitDiagram, Madge, dependency-cruiser and what replaced CodeSee, with what each one draws.+ - [Dead Code Analysis: The Best Detection Tools by Language (2026)](https://repowise.dev/blog/comparisons/best-dead-code-detection-tools): Dead code analysis tools by language: Vulture and deadcode for Python, Knip for TypeScript, Go deadcode, Java inspections, and unused dependency checkers.+ - [Git Analytics Tools: Code-Level and Team-Level, Compared](https://repowise.dev/blog/comparisons/best-git-analytics-tools): Git analytics tools compared: CodeScene, repowise and GitClear for hotspots and ownership, LinearB, Swarmia and Jellyfish for team metrics, with prices.+ - [PR Review Bots for GitHub: 6 Compared With Pricing (2026)](https://repowise.dev/blog/comparisons/best-github-pr-review-bots-2026): PR review bots for GitHub compared on price, noise and context: CodeRabbit, Greptile, Copilot code review, Codacy, Reviewdog and the repowise bot.+ - [Static Analysis Tools for Large Codebases (2026): Open Source and Commercial](https://repowise.dev/blog/comparisons/best-static-analysis-tools-large-codebases): Static analysis tools compared: SonarQube, Semgrep, CodeQL, Coverity, and the best open-source analyzers for Python, JS/TS, Java, Go, C/C++ and C#.+ - [Engineering Onboarding Tools: The Best Tools to Onboard New Engineers (2026)](https://repowise.dev/blog/comparisons/best-tools-for-onboarding-engineers): Engineering onboarding tools compared: repowise, Swimm, CodeTour, Confluence or Notion, and Stack Internal, with a stack and a scorecard by team size.+ - [repowise vs Google Code Wiki: Public Repos, Private Code and What Each Does](https://repowise.dev/blog/comparisons/repowise-vs-google-codewiki): Google Code Wiki documents public GitHub repos for free and refreshes fast. repowise adds private repos, git risk, code health and MCP tools for agents.+ - [repowise vs Sourcegraph: Code Search Compared with Docs and Git Risk](https://repowise.dev/blog/comparisons/repowise-vs-sourcegraph): Sourcegraph leads code search for large code estates, and repowise adds docs, git risk and code health. This guide shows when each one fits.+ - [Find Circular Dependencies in a Monorepo (TypeScript, Python, Go)](https://repowise.dev/blog/guides/find-circular-dependencies-monorepo): Tested commands to find circular dependencies in a monorepo: madge and dependency-cruiser for TypeScript, import-linter and pylint for Python, and Go.+ - [Generate an Architecture Diagram from a GitHub Repo: GitDiagram, Eraser and repowise Compared](https://repowise.dev/blog/guides/generate-architecture-diagram-from-github-repo): Three ways to turn a GitHub repo into an architecture diagram, checked against Flask's real import graph: what a model draws well and what it leaves out.+ - [Generate C4 Diagrams from Code Automatically (and Keep Them Current)](https://repowise.dev/blog/guides/generate-c4-diagrams-from-code): Five ways to generate C4 diagrams from source code, which C4 levels each can derive, and how to regenerate them on every push so they stop going stale.+ - [How to Learn a New Codebase in Your First Week (Day-by-Day Checklist)](https://repowise.dev/blog/guides/how-to-learn-a-new-codebase-first-week): A day-by-day checklist for learning a new codebase in your first week, with a done state for each day and questions to ask the repo before your team.

Showing the first 40 of each.