// devtools · repowise-dev/repowise

repowise

repowise é um projeto de ferramentas de desenvolvimento de código aberto de repowise-dev (repowise-dev/repowise no GitHub). Tem 7.239 estrelas no GitHub e 791 forks, é publicado sob a licença AGPL-3.0 e foi atualizado pela última vez no GitHub em 8 de outubro de 2026.

Repowise — codebase intelligence: health scores, auto-docs, git analytics and dead-code detection via MCP.

★ 7,2 mil estrelas⑂ 791 forksAGPL-3.0atualizado out 2026
▦ visual: o README deste projeto não inclui nenhuma captura incorporável,
então aqui vai um marcador. O guia abaixo está completo mesmo assim.
// dados do projeto

Dados do projeto

Estrelas no GitHub
7.239
Forks
791
Licença
AGPL-3.0
Última atualização no GitHub
8 de outubro de 2026
Tipo de ficha
Guia de instalação completo
Site oficial
Official site
// como funciona

Como funciona

  1. Clarify your goal

    Pick the repo to index and decide which front door you will use — CLI for you, MCP for your agents, or both.

  2. Get the project

    Clone repowise-dev/repowise from GitHub (or use the install path in the run steps below) and skim its README for the parts relevant to your goal.

  3. Install and configure

    Install repowise as a uv tool (or pipx/pip), then run its one-line setup in your repository to build the index.

  4. Run your first task

    Index the repo, read its health score, then ask your agent (via MCP) which files are risky to change in your next task.

// recursos

Por que as pessoas gostam tanto

Code health scores

Scores repository health and re-checks its own score after each index, so quality trends are visible, not vibes.

Auto-generated docs and agent files

Generates documentation and writes your CLAUDE.md and AGENTS.md from the real index, keeping them current.

Change-risk scoring

Scores any commit or base..HEAD range 0–10 from the shape of the change, plus bug-history per file and symbol.

Test intelligence

Works out which tests reach a file and which a diff exercises, and estimates test coverage without running coverage.

Dead code and git analytics

Dead-code detection, architectural-decision records, and analytics over git history, including which other open branches edit your files.

Agent-ready via MCP

Exposes the index through MCP, distills large command output before agents read it, and seeds new git worktrees with the index automatically.

Advertisement
// execute você mesmo

Execute você mesmo

  1. Clone the repository

    Get the source from the official GitHub repository for repowise.

    git clone https://github.com/repowise-dev/repowise.git
    cd repowise
  2. Install Repowise

    Install it as a uv tool exactly as the README's one-line setup shows (pipx and pip installs are also documented).

    uv tool install repowise
  3. Set up your repository

    Run Repowise's setup/index in your repo so the .repowise/ index is built next to the code.

    # Run the repowise setup command in your repository per the README — see README for the exact command
// casos de uso

O que você pode criar

Advertisement
// perguntas frequentes

Perguntas frequentes

Who maintains repowise?

repowise-dev, through the repowise-dev/repowise repository, with the site at repowise.dev.

Is repowise free to use?

Yes — the project is open source under the AGPL-3.0 license as recorded for this listing. See the license terms for any conditions on redistribution.

Does repowise need a paid API key?

The self-hosted open-source version runs on your machine with your own LLM provider only if you turn its prose features on; core indexing does not require a paid key.

How does Repowise compare to a linter or static-analysis tool?

Linters check code style and known bug patterns file by file. Repowise builds a repo-wide intelligence layer — health, history, risk, tests, dead code and decisions — and serves it to agents via MCP, which is context for decisions, not just diagnostics.

How do I get started with repowise?

Clone the repository (or use the documented installer), follow the install and configure steps on this page, and run the smallest real task first — index the repo, read its health score, then ask your agent (via MCP) which files are risky to change in your next task.

// continue explorando

Ferramentas semelhantes

Ferramentas de desenvolvimento

fallow

Codebase intelligence for TypeScript/JavaScript — health, duplication, dead code and architecture.

★ 5,0 mil estrelasMIT
Ver o guia →
Ferramentas de desenvolvimento

code-review-graph

Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked con…

★ 31,9 mil estrelasMIT
Ver o guia →
Ferramentas de desenvolvimento

opcode

A desktop GUI and toolkit for Claude Code - agents, sessions, analytics and MCP

★ 22,4 mil estrelasAGPL-3.0
Ver o guia →
Ferramentas de desenvolvimento

claude-context

Code-search MCP for Claude Code: make your entire codebase the context for any coding agent.

★ 12,6 mil estrelasMIT
Ver o guia →
Ferramentas de desenvolvimento

fastapi_mcp

Expose your FastAPI endpoints as Model Context Protocol tools - with authentication - in a few lines of code.

★ 12,0 mil estrelasMIT
Ver o guia →
Ferramentas de desenvolvimento

ralph-claude-code

An autonomous loop for Claude Code with intelligent exit detection, rate limits and a circuit breaker.

★ 9,7 mil estrelasMIT
Ver o guia →
// alternativas

Alternativas em Ferramentas de desenvolvimento

Os outros projetos de Ferramentas de desenvolvimento com mais estrelas no catálogo do LibreAI — a lista realista de alternativas se repowise não for o ideal para você.

// mais em devtools

Mais em Ferramentas de desenvolvimento

Projetos de Ferramentas de desenvolvimento próximos no catálogo, os mais próximos em estrelas de repowise: continue explorando dos dois lados dele.

Baixe o repowise

Grátis e aberto: pegue o código-fonte, dê uma estrela no repositório e comece a criar.