Repovine

io.github.legann由 GitHub 账号 legann 发布v0.1.1更新于 Oct 25, 2026

Checkout-local repository context graph over MCP; `npx repovine setup` wires skills, agents, hooks.

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

Repovine 在本地检出目录中构建仓库上下文图，并通过 MCP 提供给编码助手，用于代码导航、运行时流程追踪和依赖分析。

可以做什么
搜索、映射和检查仓库图，定位代码与包并查看其内容。查找入口点并追踪请求或订单在服务间的流转。分析依赖影响范围以及组件读取的环境变量等配置面。检查架构中的边界违规和过大的模块。读取、写入、合并和校验挂在图节点上的版本化注解，并重建或检查图状态。
适用场景
适用于编码助手在大型或多包仓库中工作、需要关于结构、依赖、运行时流程和配置的结构化上下文而非逐文件搜索的场景。最适合 TypeScript 以及受支持的框架或基础设施仓库。
运行要求
通过 npx 作为本地 stdio 进程运行，需要 Node.js 22 或更高版本。仓库需有可索引的根：tsconfig.json、pyproject.toml 或 setup.py（需要 python3），或受支持的 IaC 文件。需按客户端（claude、codex、cursor 或 all）执行 setup，会写入工作区文件。
安装前请注意
setup 会向工作区添加技能、子代理、钩子和指令文件，并修改客户端配置，尽管其声称会保留现有设置。注解工具会写入版本化的知识文件，这些文件预期提交到 Git。项目为 0.1.0 预览版，图结构和插件 SDK 仍会变动。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Repovine，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

repovine

[CI] [npm]

Repository context assembled and conveyed to coding agents.

The repository knowledge layer

A repository-agnostic core. Across supported languages, frameworks, and infrastructure formats, repovine normalizes repository structure into one queryable model.

Contract boundaries by design. The graph connects repository units through shared code, template, and runtime contracts. These boundaries support repository-scale navigation, dependency impact, runtime flow, and configuration.

Versioned knowledge with explicit ownership. Version-controlled annotations attach intent, invariants, risks, and operational knowledge to graph nodes. Agents and developers author them; repovine checks freshness and structural consistency against repository state.

Together, these layers support intent-driven, context-compiled, contract-verified development. Task intent guides MCP context assembly, and observable claims are checked against repository state.

Checkout-local by design. The live graph and indexes are built from each checkout's working tree and run in memory. Configuration and authored knowledge travel through Git. No database is required.

Benchmarks. Across correctness and restraint tasks drawn from public software repositories, 90% of Repovine runs passed their case-specific diff gate, compared with 10.6% of baseline runs. Explore the results.

Quick start

Start in an existing repository:

bash
npx repovine setup claude # or codex, cursor, all

setup connects the selected client to repovine, adds repovine skills, hooks, and instructions, and builds the repository graph.

The graph model

repovine deterministically derives a graph of cross-unit contracts from repository state. Source and infrastructure plugins translate stack-specific structures into the same vocabulary of packages, modules, exported symbols, templates, runtime resources, and their relationships—so navigation, dependency impact, runtime flow, and configuration work consistently across supported stacks. Explore the design rationale.

How it works

The engine and MCP provide the base workflow. Interactive clients use it directly. For explicit protocol runs, Delivery Protocol adds a structured assignment → result → compliance contract around the same workflow.

Client

In clients such as Claude Code, Codex, or Cursor, the agent uses repovine MCP directly while the developer stays in the loop.

mermaid
graph LR  SRC["sources"] --> S1["Stage 1: gather facts"]  S1 --> S2["Stage 2: build graph"]  S2 --> ANN["versioned annotations on graph nodes"]  A["agents and developers"] --> ANN  S2 --> S3["Stage 3: build search index"]  ANN --> S3  S3 --> MCP["MCP tools"]  ANN --> MCP  MCP -->|"bounded context"| C["Cursor, Claude Code, or Codex"]
StageInputOutput
Stage 1: gather factssourcesexports, imports, env names, routes, infra
Stage 2: build graphfactspackages → modules → symbols; infra/template/domain edges
annotationsgraph + agent/developer writesversioned intent, invariants, risks, side effects, and operational constraints
Stage 3: build search indexgraph + annotationstoken index; optional embeddings to assist fuzzy search
MCPgraph + annotations + indexbounded graph and annotation query results

Delivery Protocol

Delivery Protocol defines the assignment → structured result → compliance report contract. Core owns the schemas, projections, and validators that ground the protocol in observable repository state.

The agent uses MCP to access repository context while it works. The repovine CLI validates the assignment and result and produces the compliance report.

mermaid
graph LR  IN["assignment"] --> AV["assignment validation"]  AV --> A["agent"]  A <-->|"repository context during the run"| MCP["repovine MCP"]  A --> R["structured result"]  AV -->|"validated assignment"| V["repovine compliance validation"]  R --> V  S["observable repository state + recorded context"] --> V  V --> OUT["compliance report"]

repovine validates schema conformance, assignment linkage, and claims it can recompute from the graph, annotations, recorded MCP context, and an optional revision delta. The compliance report covers protocol conformance and repository grounding; behavioral correctness and merge readiness are outside the protocol's scope.

The runnable LangGraph harness demo applies the protocol in an end-to-end agent workflow. Its orchestration topology, sandbox, retries, worktree isolation, and provider behavior are demo-specific implementation choices. See the Delivery Protocol integration guide.

MCP tools

Each tool returns a scoped, structured response.

Query tools, with typical questions for a large repository:

GroupExample questionTools
Navigatewhere is authentication? what is inside the billing package?search_context, map_context, inspect_node
Runtimewhat are the entrypoints? how does an order flow through services?get_entrypoints, trace_flow
Contracts & configwhich consumers are affected by an API change? which environment variables does the worker read?analyze_dependencies, get_config_surface
Architectureare there boundary violations or god modules?analyze_architecture

Maintenance tools service the graph and annotations:

GroupPurposeTools
Memorywhich nodes are annotated or stale?get_annotation_status, write_annotation, merge_annotations, validate_annotations, get_annotation_merge_status
Syncrebuild and check the graphrefresh_context, get_build_status, get_context_session_quality
Domainstune the domain configsuggest_domains_config
Declinesdismiss reviewed advisory itemsdecline_advisory (kind: domains-config | carrier-link-gaps)

Setup and CLI

setup adds the following repovine integrations to the workspace while preserving existing configuration and project specialists:

IntegrationIncluded
MCP serverthe repovine MCP tools
Skillsrepovine-workflow, repovine-annotations, repovine-refresh, repovine-review, repovine-status
Subagentsrepovine-repo-explorer, repovine-annotation-writer, repovine-architecture-auditor, repovine-code-reviewer
Hookspre-edit boundary notice, post-edit stale-graph notice, session-start "MCP first" reminder
InstructionsAGENTS.md (Cursor uses .cursor/rules)
CommandGoal
npx repovinerun the stdio MCP server outside an IDE/CLI client
npx repovine setup cursor (or claude/codex/all)add the integrations above, then build the graph
npx repovine buildbuild the graph
npx repovine statusgraph / config / annotation health
npx repovine doctordiagnose the workspace integration
npx repovine clearremove repovine-managed workspace files
npx repovine --version · --helpversion / help
npx repovine delivery --helpharness/CI Delivery Protocol commands: descriptor, manifests, run brief, validation, and compliance
npx repovine agents --helpharness/CI utilities for repository roles, deterministic orientation, and context-session quality

STDIO is the only supported MCP transport in v1. For remote, devcontainer, WSL, VM, or devbox use, launch the repovine subprocess inside that environment so it runs in the checkout being analyzed.

Supported stacks

AreaSupport
LanguagesFirst-class support: TypeScript (JS/JSX via the TS toolchain, needs tsconfig.json); Python partial (backend routes + server-rendered templates)
FrameworksReact, Next.js, Nuxt, SvelteKit, Angular, NestJS, serverless monorepos; Vue/Svelte single-file components (script blocks only)
IaCPartial, expanding coverage: SAM/CloudFormation, Terraform, Kubernetes, Helm, Dockerfile, docker-compose, Vercel

IaC parsers turn infra files into runtime-resource nodes plus links to the code and images behind them. They cover selected resources and relationships rather than complete format schemas. Coverage is under active development, and extending the existing extractors is a contribution area. Design detail: DESIGN.md.

Requires Node.js 22+ and one indexable root: tsconfig.json, pyproject.toml/setup.py (needs python3), or IaC files. Repositories with supported IaC files can be indexed without a source project; the graph contains infrastructure modules and runtime resources, but no code modules.

Repository files

File / dirGitRole
repovine.config.jsoncommitmain config: graph build and MCP output
repovine.domains.jsoncommitlogical organization of the repository graph
repovine.annots.jsoncommitsemantic annotation memory
.repovine/ignorelocal engine cache and workspace state

Defaults work for most TypeScript repositories. Config reference: docs/workspace-files.md.

Status

Preview (0.1.0), usable today and open to contributions. The graph schema and @repovine/plugin-sdk still change.

Contribute

repovine's plugin architecture provides two public producer surfaces for extending language and infrastructure coverage, both exposed by @repovine/plugin-sdk:

PluginWhat it adds
Language source producera language: source files → modules, imports, exports, semantic hints
IaC parseran infra format: files → runtime-resource nodes and links

Built-in and third-party producers share the same public plugin contracts; core validates their output and owns graph identities and ontology. See the plugin guide and runnable Go source plugin, IaC plugin, and other examples.

Learn more

  • DESIGN.md: system boundaries, graph contract, trust model, and limitations
  • CONTRIBUTING.md: dev setup, quality gates
  • Documentation: guides, references, and the TODO app walkthrough
  • Platform support: per-surface OS tiers, prerequisites, and promotion rules
  • examples: runnable plugins and the Delivery Protocol harness demo

License

MIT. See LICENSE.

来源：README.md，提交 9a7b08f

工具

0
SourceWeft 尚未在沙箱中启动过该软件包，因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手；SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分