Repo Test Architect

MCP开发工具

提供方 RepoAssay · 包名 repo-test-architect

开发工具 stdio · 本地进程 会话登录 社区 / 第三方 ClaudeCodexZed
查看接入方式

Local-first, read-only MCP server for evidence-backed repository test architecture audits and test planning.

一句话选型结论

按资料字段整理

Repo Test Architect 属于开发工具类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude、Codex、Zed,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

testing repository analysis static analysis code quality local first

支持客户端

适用场景

testingrepository analysisstatic analysis

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
npx --yes repo-test-architect mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 node,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Repo Test Architect当前 未标注 stdio · 本地进程 本地部署 有 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方RepoAssay上游标注的维护方 RepoAssay
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时repo-test-architect · node本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

25.8 KB
来自项目仓库与上游目录的原文,未做删改

Repo Test Architect

Audit-first test strategy tooling for codebases.

Repo Test Architect builds a deterministic audit graph before asking any model or agent to reason about tests. The goal is to identify repo-native, high-value test work from facts the tool can inspect locally: project roots, framework signals, existing tests, source classifications, blockers, and remaining risk.

The current implementation can:

  • audit JavaScript/TypeScript, PHP, Python, Ruby, and Swift projects through supported adapters
  • audit supported, bounded Kotlin/JVM fixtures through the same shared artifact model
  • audit conventional Go modules and literal repository-contained go.work members through a supported bounded adapter
  • audit conventional Cargo packages and literal repository-contained workspace members through a supported bounded Rust adapter
  • audit one conventional SDK-style C# test project or one unique literal production/test project edge, including bounded native xUnit MTP-v2 and MSTest.Sdk v4 ownership, literal and one-hop root-aliased target frameworks, one repository-contained direct *.cs compile include, finite target-conditioned package shapes, bounded nearest-file build and central-package props, exact immutable test-field receivers, stable direct-call results, inline out results, framework exception and collection/string assertions, one-hop test helpers, and guarded well-known System type collisions, through a supported bounded .NET adapter
  • audit one conventional Composer/PSR-4 project with PHPUnit through a supported bounded PHP adapter
  • audit one conventional Mix application with exact MixProject/Mixfile, bounded source and Mix-task ownership, literal local ExUnit wrapper discovery, and test-body evidence through a supported bounded Elixir adapter
  • detect polyglot project roots and report unsupported ecosystems without hiding them
  • produce a complete repository analysis, findings, ranking, plan, execution hints, and verification commands in one audit pass
  • classify source files by likely test value and defer low-value direct tests
  • rank candidates and generate test plans from the audit graph
  • derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints without selecting models or spawning subagents
  • analyze conservative test placement findings across project boundaries
  • collect project-level stats for coverage, candidate counts, frameworks, commands, and adapter usage
  • provide disabled-by-default local MCP diagnostics, safe internal-error report IDs, runtime checks, and inspectable sanitized bundles without external reporting
  • expose the same deterministic behavior through CLI commands, a local invoke harness, and a stdio MCP SDK server
  • lock behavior with golden snapshots, model-consistency scenarios, package checks, and cross-OS CI

Native test generation is intentionally deferred. generate_selected_test returns a structured deferred artifact until adapter-specific generation policy and repair-loop fixtures exist.

Repo Test Architect 1.0.0 is available on npm as latest and in the Official MCP Registry, with stable support for the documented CLI, MCP tools, configuration and versioned artifact contracts. Treat its findings as evidence-backed review input rather than an automatic instruction to change a repository. See the 1.0.0 release notes for changes, compatibility and publication status.

Ten adapters are supported within their documented boundaries. Dart/Flutter remains experimental, and native test generation remains deferred.

Maintenance is provided as time permits, with no guaranteed response time or feature schedule. Focused community PRs are welcome; see Contributing and Support.

Install

Node.js 20 or newer is required.

Run the CLI without a global install:```sh
npx --yes repo-test-architect doctor
npx --yes repo-test-architect analyze .


Pin the stable version:```sh
npx --yes repo-test-architect@1.0.0 doctor
npx --yes repo-test-architect@1.0.0 analyze .

Or install the CLI and MCP server binaries:```sh
npm install --global repo-test-architect
repo-test-architect doctor
repo-test-architect analyze .


Add the local stdio MCP server to an MCP-capable client:```json
{
  "mcpServers": {
    "repo-test-architect": {
      "command": "npx",
      "args": [
        "--yes",
        "repo-test-architect",
        "mcp"
      ]
    }
  }
}

To keep an MCP client on this exact release, pin its version:```json
{
"mcpServers": {
"repo-test-architect": {
"command": "npx",
"args": [
"--yes",
"repo-test-architect@1.0.0",
"mcp"
]
}
}
}


The client launches the server locally. Repository source stays on the machine unless the client or another configured tool sends it elsewhere. Connected models receive instructions to start with `analyze_repository` for a general repository review. See MCP client config and agent install paths for global-install, local-checkout, and host-specific guidance.

## Quick Start

For a human-readable review of the current repository:```sh
npx --yes repo-test-architect analyze .

analyze detects every project root, runs each supported adapter once, and derives the audit summary, top findings, candidate ranking, test plan, execution hints, project stats, and verification commands. Markdown stays compact; JSON preserves the complete evidence bundle:```sh
npx --yes repo-test-architect analyze . --format json
npx --yes repo-test-architect analyze . --changed


Useful focused views:

| Goal | Command |
| --- | --- |
| Complete repository review | `repo-test-architect analyze .` |
| Concise architecture findings | `repo-test-architect findings-projects .` |
| Actionable cross-project plan | `repo-test-architect plan-projects .` |
| Raw reusable project audits | `repo-test-architect audit-projects . --format json` |
| Runtime readiness | `repo-test-architect doctor` |

Run `repo-test-architect --help` for the short command map or `repo-test-architect  --help` for options. The CLI reference documents the full surface.

For an MCP-connected model, the equivalent default is `analyze_repository`. Use narrower tools only when the request asks for one artifact or already supplies an audit artifact.

## Current Scope

Available adapters:

- `dart` (experimental): Dart and Flutter pubspec packages, conventional `package:test` and `flutter_test` entrypoints, exact library-import evidence, widget test recommendations, and bounded `dart test` / `flutter test` commands; see Dart and Flutter support
- `csharp`: one static SDK-style test project or one unique literal production/test project edge, including bounded native xUnit MTP-v2 and MSTest.Sdk v4 ownership, exact literal or one-hop root-aliased target membership, one repository-contained direct `*.cs` compile include, finite project-local target-conditioned package predicates, and a pair selected amid unrelated projects, with bounded nearest-file `Directory.Build.props` metadata and static `Directory.Packages.props` versions, xUnit, NUnit, or MSTest attributed tests, exact project-file commands, runnable-body-owned direct type calls, bounded concrete-local or immutable test-field receivers, one-hop stable direct-call, receiver-call, or inline `out var` result assertions, bounded exception assertions, and one same-class private-static test-helper hop; see the C# alpha support matrix
- `elixir`: one conventional Mix application with literal app and exact MixProject/Mixfile ownership, conventional/app-prefixed modules and protocols, exact Mix tasks, bounded acronym, terminal-plural, repeated-declaration, and compiled local ExUnit-wrapper ownership, static startup options, test-body-scoped direct fully qualified or exact-alias calls, conservative filename evidence, and a blocker-free `mix test` command; see Elixir alpha support
- `javascript`: JavaScript/TypeScript repositories with Node's test runner (including TypeScript execution scripts), Bun test, AVA, Mocha/CommonJS, Vitest, Jest, Playwright, Cypress, Express/Supertest, React Testing Library detection, and bounded literal browser request-to-route evidence; see the alpha support matrix for evidence boundaries and known gaps
- `go`: conventional `go.mod` projects and literal repository-contained `go.work` members using runnable standard-library `TestXxx`, `FuzzXxx`, or `ExampleXxx` tests, package-local filename, unique top-level and parser-owned concrete receiver-method symbols through explicit types, exact simple constructor results, or exact statically typed test-helper results, bounded standard-library and Testify assertion usage, parser-scoped local shadow checks, same-package or exact external-package imports (including dot imports), generic top-level functions, and bounded callable-body-owned same-package or module-local source hops, module-local commands, and optional explicit `GOOS`/`GOARCH`/custom-tag selection; see the alpha support matrix for the supported boundary and blockers
- `kotlin`: conventional Gradle/Maven JVM module roots, settings-owned Gradle aggregates, and root-declared Maven reactors with Kotlin and/or Java standard source sets, dependency-qualified direct/exported-transitive module evidence, JUnit 4/5, `kotlin.test`, bounded Gradle/JUnit Platform Kotest common specs, conventional Gradle/Spock features, and method-level TestNG through direct Maven dependencies or Gradle `useTestNG()`; see the Kotlin/JVM alpha support matrix
- `php`: one root Composer project with literal string-valued PSR-4 source/test ownership, bounded literal autoloaded function files, statically declared PHPUnit, exact bounded commands or explicit safe command withholding, conventional runnable test classes including one unique source- or test-owned PHPUnit base edge, direct imported or exact same-namespace class calls, and conservative basename fallback; see PHP alpha support
- `python`: bounded Python package, FastAPI, Django, and Flask layouts with declarative multi-package/namespace ownership, configured pytest discovery, exact absolute/relative imports, one-hop source dependency evidence, static framework test-client route evidence, pytest/unittest, async and property-based extensions, fixture reachability, pip/setuptools, uv, Poetry, Hatch, tox, nox, and coverage configuration; see the Python alpha support matrix
- `rust`: conventional Cargo packages and literal repository-contained workspace members using the built-in `#[test]` harness, inline `#[cfg(test)]` modules, exact exclusion of external test-only module graphs, exact crate-module imports from `tests/`, and exact unconditional crate-root symbol re-exports; see the Rust alpha support matrix
- `ruby`: one conventional Bundler project with `lib/` sources, one root gemspec or a complete exact named root-gemspec set, runnable `Minitest::Test` `test_*` methods or RSpec examples, exact bounded commands, root `.rspec` and exact per-file `spec_helper` loading, three-edge literal require/unique-constant evidence, exact singleton calls, exact constant-owned RSpec `described_class`, direct immutable constructor-local, one-line RSpec `let`/`subject`, exact source-factory and same-group RSpec helper receivers, and exact same-file literal shared-example inclusion, bounded assertion usage, conservative basename fallback, and explicit Minitest-spec/Rails/mixed-runner blockers; see the Ruby alpha support matrix
- `swift`: Swift Package Manager, Xcode-style and Bazel/rules_swift layouts, Swift Testing, XCTest, Quick/Nimble, SnapshotTesting, VaporTesting/XCTVapor, reactive frameworks, and generic Fluent database boundaries with driver-specific qualifiers; see the Swift alpha support matrix

Project detection reports Elixir Mix roots through the supported bounded adapter. Unsupported ecosystems remain visible so clients can distinguish "not audited yet" from "not present."

Don't see your stack? Open an adapter request with the language or ecosystem, build system, test frameworks, and—when possible—a representative public repository. Requests help prioritize adapters against real repository shapes and user demand.

The public package exposes the audit CLI, the stdio MCP server, and a deterministic MCP invoke harness under the stable binary names documented below.

## Advanced CLI and Contributor Reference

The commands below expose focused artifacts, fixtures, evals, diagnostics, and release checks for advanced use and repository development.

Show the complete command and development reference

Run the complete analysis directly or against the polyglot example:```powershell
npm run analyze
npm run analyze:json
npm run analyze:example
npm run analyze:example:json

Check runtime and diagnostics readiness:```powershell
npm run doctor
npm run doctor:json


Local MCP diagnostics are disabled by default. They can be explicitly directed to stderr or a bounded local JSONL file; see Local diagnostics. Build a sanitized, inspectable bundle with:```powershell
npm run diagnostic-bundle -- --diagnostics-file ./.repo-test-architect/diagnostics.jsonl --format json
node ./src/cli/index.js diagnostic-bundle --diagnostics-file ./.repo-test-architect/diagnostics.jsonl --format json

List registered adapters:```powershell
npm run adapters
npm run adapters:json


Inspect project detection marker rules:```powershell
npm run detect-rules
npm run detect-rules:json

Detect project roots and adapter matches:```powershell
npm run detect:example
npm run detect:example:json
npm run detect:kotlin-fixture
npm run detect:kotlin-fixture:json
npm run detect:apple-fixture
npm run detect:apple-fixture:json
npm run audit-projects:example
npm run audit-projects:example:json
npm run audit-projects:changed-since
npm run summarize-projects:example
npm run summarize-projects:example:json
npm run rank-projects:example
npm run rank-projects:example:json
npm run plan-projects:example
npm run plan-projects:example:json
npm run hints-projects:example
npm run hints-projects:example:json
npm run findings-projects:example
npm run findings-projects:example:json
npm run placement-projects:example
npm run placement-projects:example:json
npm run placement-projects:split-example:json
npm run stats-projects:example
npm run stats-projects:example:json


For project-aware self-audits, exclude checked-in fixture or sample roots with a quoted subtree pattern:```powershell
node ./src/cli/index.js findings-projects . --exclude-project "examples/**"

Reuse a saved project audit artifact:```powershell
node ./src/cli/index.js audit-projects ./examples/polyglot-workspace --format json
node ./src/cli/index.js summarize-projects --from-project-audits ./project-audits.json --format json
node ./src/cli/index.js rank-projects --from-project-audits ./project-audits.json --format json
node ./src/cli/index.js plan-projects --from-project-audits ./project-audits.json --format json
node ./src/cli/index.js findings-projects --from-project-audits ./project-audits.json --format json
node ./src/cli/index.js placement-projects --from-project-audits ./project-audits.json --format json
node ./src/cli/index.js stats-projects --from-project-audits ./project-audits.json --format json
``````powershell
npm run audit:example
npm run audit:kotlin-fixture


Output the structured audit graph:```powershell
npm run audit:example:json
npm run audit:kotlin-fixture:json

Generate an actionable test plan from the audit graph:```powershell
npm run plan:example
npm run plan:example:json
npm run hints:example
npm run hints:example:json
npm run plan:kotlin-fixture
npm run plan:kotlin-fixture:json
npm run plan:item:example
npm run plan:changed
npm run plan:changed-since


Derive advisory execution hints while leaving the plan artifact unchanged:```powershell
node ./src/cli/index.js hints ./examples/node-vitest-basic --item add-test:src/authService.ts
node ./src/cli/index.js hints-projects ./examples/polyglot-workspace --format json

The installing CLI or agent host remains responsible for model choice, budgets, permissions, context loading, and subagent lifecycle.

Explain one audited target by stable target ID:```powershell
npm run explain:example


Rank test candidates without generating tests:```powershell
npm run rank:example

Analyze existing test placement from audit evidence:```powershell
npm run placement:example
npm run placement:example:json
npm run placement:from-audit:example


Exercise the MCP-style tool surface:```powershell
npm run mcp:tools
npm run mcp:analyze:example
npm run mcp:adapters
npm run mcp:detect-rules
npm run mcp:detect:example
npm run mcp:audit-projects:example
npm run mcp:summarize-projects:example
npm run mcp:rank-projects:example
npm run mcp:plan-projects:example
npm run mcp:findings-projects:example
npm run mcp:placement-projects:example
npm run mcp:placement-split:example
npm run mcp:stats-projects:example
npm run mcp:audit:example
npm run mcp:audit:kotlin-fixture
npm run mcp:placement:example
npm run mcp:audit:envelope
npm run mcp:stdio
npm run mcp:smoke

Generate a plan from an existing audit JSON file:```powershell
npm run plan:from-audit:example


Run the auditor regression tests:```powershell
npm test
npm run alpha:check
npm run release:check

Find and rank active public repositories for real-world adapter validation:```powershell
npm run validation:repos -- --profile react
npm run validation:repos -- --profile workspace --limit 10
npm run validation:repos -- --profile swift,gradle,maven --format json


The finder uses authenticated GitHub repository search, verifies exact ecosystem markers in root manifests, and ranks candidates using maintenance recency, stars, repository size, lockfiles, CI, and license metadata. Run `npm run validation:repos -- --list-profiles` for the available profiles and `--help` for quality-filter options.

Check that every supported adapter has a complete, pinned hardening corpus:```powershell
npm run corpus:check
npm run corpus:scorecard
npm run corpus:measure -- --case python-asyncer --checkout /path/to/pinned/asyncer
npm run corpus:measure -- --case python-django --checkout /path/to/pinned/django --profile-phases
npm run csharp:performance:check
npm run javascript:performance:check
npm run python:performance:check
npm run kotlin:performance:check
npm run rust:performance:check
npm run swift:performance:check
npm run go:performance:check
npm run ruby:performance:check
npm run php:performance:check

The versioned evals/validation-corpus.json manifest records one conventional library or service, one framework-heavy application, and one difficult ownership graph per adapter cohort. Every supported adapter must have a complete cohort; a registered experimental adapter may be added only with all three roles. Each record carries the shared detection, ownership, command, evidence, ranking, stability, and performance scorecard. The 33 current pins span ten supported adapters and experimental Dart, with all 231 bounded scorecard areas passing. Dart live validation also records native upstream suite results and remaining limits. A reviewed command may be null when the adapter correctly withholds unsafe execution. Cases may also carry bounded adapter audit options, such as an explicit Go build target, so repeated measurements remain host-independent.

corpus:scorecard renders the review contract for humans. It reports review completeness separately from the pass rate among reviewed checks and keeps PASS, FAIL, and PENDING visible for every area. Use npm run corpus:scorecard -- --format json for the deterministic validation-scorecard/v1 view. These are validation-review results, not a repository-quality rating.

corpus:measure verifies the checkout's exact pinned Git SHA, runs the selected adapter at least three times, rejects canonical audit drift, and reports the raw durations, median duration, evidence-link count, and normalized audit digest used to update the scorecard. For the exact Python and Swift pins, --profile-phases defaults to five runs and additionally reports ordered samples and medians for traversal/text reading, project/build ownership, source discovery/indexing, test parsing/indexing, and evidence/classification/artifact assembly. These development timings are callback-only and never enter audit/v1, CLI/MCP audit output, or local MCP diagnostics.

Each adapter performance check separately runs a generated 400-source/200-test project, verifies its candidate and evidence counts, and enforces a broad cross-platform regression ceiling. The Rust gate includes one additional skipped src/lib.rs module-wiring target required to declare the 400 behavioral modules. These synthetic gates complement the recorded per-repository corpus distributions.

Use alpha:check for the adapter-support milestone. release:check additionally covers packaging and installed-binary readiness.

The CI workflow keeps one stable Linux pr-gate: documentation-only changes run focused contract tests, normal changes run npm run alpha:check, and distribution-sensitive changes run npm run release:check. Windows runs only for runtime and portability changes; macOS runs only for Swift-sensitive changes. A merge to master runs the complete release gate on Linux, while manual dispatch runs the full release gate on all three operating systems.

The tests include golden audit and plan snapshots under evals/expected, driven by evals/fixtures.json, plus shared adapter-conformance checks for deterministic JSON, portable paths, evidence semantics, and downstream artifact agreement.
JSON schemas and the signal registry for versioned artifacts live under schemas/.

Refresh snapshots after intentional audit behavior changes:```powershell
npm run eval:check
npm run eval:summary
npm run eval:test
npm run eval:update


Check model-consistency scenario locked fields against deterministic tool results:```powershell
npm run model-consistency:check
npm run model-consistency:json
npm run model-consistency:json -- --profile local-small
npm run model-consistency:compare -- baseline-summary.json candidate-summary.json
npm run model-consistency:stats

Node 20 or newer is required for the CLI. The default smoke check is portable across platforms:```powershell
npm run smoke


If Node is not available yet, the repository still includes a PowerShell smoke check:```powershell
powershell -ExecutionPolicy Bypass -File ./scripts/smoke.ps1

Check package contents before publishing:```powershell
npm run pack:check
npm run bin:check
npm run installed-package:check
npm run distribution:check
npm run release:check


`distribution:check` validates packaging and MCP metadata preparation. The stricter `distribution:check:publish` verifies that the public npm and MCP Registry identities are aligned before a release. See Distribution.

## Shape```txt
src/
  core/
    audit-model.ts
    audit-phase-timing.js
    plan-execution-hints.js
    plan-execution-hints.ts
    repository-text-files.js
    report.js
    report.ts
  diagnostics/
    diagnostics.js
  adapters/
    csharp/
      audit.js
    javascript/
      audit.js
      audit.ts
    kotlin/
      audit.js
    python/
      audit.js
    rust/
      audit.js
    swift/
      audit.js
  cli/
    index.js
examples/
  csharp-sdk-project-pair/
  csharp-sdk-unique-pair/
  csharp-sdk-xunit-basic/
  node-vitest-basic/
  express-supertest/
  react-testing-library/
  kotlin-junit-basic/
  kotlin-gradle-groovy-junit/
  kotlin-gradle-module-graph-junit/
  kotlin-maven-junit/
  kotlin-maven-reactor-junit/
  kotlin-maven-wrapper-junit4/
  kotlin-gradle-aggregate-kotest/
  kotlin-gradle-spock/
  kotlin-maven-testng/
  python-pytest-service/
  python-uv-pytest/
  python-poetry-pytest/
  rust-cargo-basic/
  rust-cargo-workspace-basic/
  swift-spm-xctest/
  swift-spm-swift-testing/
  swift-spm-quick-nimble/
  swift-spm-custom-paths/
  swift-spm-alternate-roots/
  swift-bazel-xctest/
  swift-xcode-test-plans/
  vapor-service-tests/
  vapor-mongodb-boundaries/
evals/
  expected/
  model-consistency/
schemas/

Important runtime surfaces:

  • CLI: src/cli/index.js
  • MCP tool definitions: src/mcp/tool-definitions.js
  • stdio MCP SDK server: src/mcp/stdio.js
  • local invoke harness: src/mcp/invoke.js
  • release gate: scripts/check-release-readiness.js

Docs

  • Contributing
  • Support
  • Security policy
  • Project plan
  • Project status
  • Public readiness
  • Alpha readiness
  • Real repository audit reports
  • Product positioning
  • Near-term roadmap
  • Adapter hardening plan
  • August 2026 adapter portfolio analysis
  • Shared audit kernel inventory
  • Demo script
  • Decision log
  • Second adapter spike
  • Kotlin/JVM alpha support
  • Go alpha support
  • Go validation hunt report
  • Go HTTP validation report
  • Go workspace ownership validation report
  • Go dot-import validation report
  • Go constructor-result validation report
  • Go cross-package source validation report
  • Go assertion-usage validation report
  • Go parser-scoped binding validation report
  • Go receiver and callable ownership validation report
  • Go test-helper receiver validation report
  • Rust alpha support
  • Ruby alpha support
  • PHP alpha support
  • PHP brick/math live validation report
  • PHP Guzzle live validation report
  • PHP Ramsey UUID live validation report
  • PHP Monolog post-promotion validation report
  • Elixir Jason live validation report
  • Elixir Plug live validation report
  • Elixir Absinthe live validation report
  • Ruby rubyzip live validation report
  • Ruby Faraday live validation report
  • Ruby Factory Bot live validation report
  • Ruby Diplomat live validation report
  • Ruby helper/factory return live validation report
  • Ruby shared-example live validation report
  • Ruby Licensed post-promotion validation report
  • C# alpha support
  • C# TDD live validation report
  • C# Sharp Cast live validation report
  • C# Glob live validation report
  • C# central packages live validation report
  • C# multi-target live validation report
  • C# target-conditioned packages live validation report
  • C# Microsoft.Testing.Platform v2 live validation report
  • C# MSTest.Sdk v4 live validation report
  • Kotlin/JVM validation hunt report
  • Adapter contract
  • Artifact contract
  • CLI reference
  • Project detection
  • Polyglot workflow
  • MCP tool surface
  • MCP client config
  • MCP deployment
  • Local diagnostics
  • Agent install paths
  • Release lifecycle
  • Release checklist

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Repo Test Architect 怎么安装?

在客户端按下面的安装命令接入:npx --yes repo-test-architect mcp。对应的包名是 repo-test-architect。装完在客户端配置里引用同一个包或端点。

Repo Test Architect 怎么在 Claude、Codex、Zed 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Repo Test Architect 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Repo Test Architect 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Repo Test Architect 支持哪些客户端?

资料标注支持 Claude、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Repo Test Architect 能提供哪些能力?

资料显示能力标签包括 testing、repository analysis、static analysis、code quality、local first。具体工具清单以官方文档为准。

Repo Test Architect 需要什么运行环境?

运行时为 node;属于本地进程,需要在本机装好运行环境。

Repo Test Architect 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。