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 分