Repo Test Architect

io.github.RepoAssay由 GitHub 账号 RepoAssay 发布v1.1.0更新于 Oct 30, 2026

Audit-first test strategy MCP server for repository-native test planning.

已验证STDIO仅桌面开发者工具数据与分析

概览

AI 生成的概览

本地 stdio MCP 服务器,审计代码仓库并生成确定性的测试计划、发现项、排序与执行提示。

可以做什么
  • 检测项目根目录,列出语言适配器与检测规则
  • 执行完整仓库审计,返回摘要、阻塞项、发现项、排序、计划、执行提示与验证命令
  • 审计单个指定项目根或所有已检测根,产出可复用的审计产物
  • 基于已有审计产物做汇总、排序、发现项与统计收集,并生成测试计划
  • 解释单个目标的证据与风险,并给出建议性测试放置发现
  • 不生成测试代码,仅返回延后处理的占位结果
适用场景
适合让助手在陌生或多语言仓库中先审查测试架构,并基于证据提出贴合仓库的测试工作建议。适用于首轮审计与规划,而非生成或运行测试。
运行要求
由 MCP 客户端以本地 stdio 进程启动,通常通过 npx;需要 Node.js 20 或更高版本。未声明账号、API 密钥、环境变量或请求头。它会读取本机仓库文件。
安装前请注意
审计结论仅作为评审参考,不应视为修改仓库的指令。原生测试生成功能已停用,generate_selected_test 只返回延后结果。不支持的项目与失败的适配器会表现为覆盖缺口。除非客户端或其他已配置工具外发,仓库源码保留在本机。

安装

在 SourceWeft 中

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

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

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Repo Test Architect logo]

Repo Test Architect

[Repo Test Architect MCP server]

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.1.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.1.0 release notes for per-project failure containment, skipped-test handling, artifact validation, compatibility notes and publication status, and the 1.0.0 release notes for the stable contract.

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 doctornpx --yes repo-test-architect analyze .

Pin the stable version:

sh
npx --yes [email protected] doctornpx --yes [email protected] analyze .

Or install the CLI and MCP server binaries:

sh
npm install --global repo-test-architectrepo-test-architect doctorrepo-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",        "[email protected]",        "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 jsonnpx --yes repo-test-architect analyze . --changed

Useful focused views:

GoalCommand
Complete repository reviewrepo-test-architect analyze .
Concise architecture findingsrepo-test-architect findings-projects .
Actionable cross-project planrepo-test-architect plan-projects .
Raw reusable project auditsrepo-test-architect audit-projects . --format json
Runtime readinessrepo-test-architect doctor

Run repo-test-architect --help for the short command map or repo-test-architect <command> --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 analyzenpm run analyze:jsonnpm run analyze:examplenpm run analyze:example:json

Check runtime and diagnostics readiness:

powershell
npm run doctornpm 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 jsonnode ./src/cli/index.js diagnostic-bundle --diagnostics-file ./.repo-test-architect/diagnostics.jsonl --format json

List registered adapters:

powershell
npm run adaptersnpm run adapters:json

Inspect project detection marker rules:

powershell
npm run detect-rulesnpm run detect-rules:json

Detect project roots and adapter matches:

powershell
npm run detect:examplenpm run detect:example:jsonnpm run detect:kotlin-fixturenpm run detect:kotlin-fixture:jsonnpm run detect:apple-fixturenpm run detect:apple-fixture:jsonnpm run audit-projects:examplenpm run audit-projects:example:jsonnpm run audit-projects:changed-sincenpm run summarize-projects:examplenpm run summarize-projects:example:jsonnpm run rank-projects:examplenpm run rank-projects:example:jsonnpm run plan-projects:examplenpm run plan-projects:example:jsonnpm run hints-projects:examplenpm run hints-projects:example:jsonnpm run findings-projects:examplenpm run findings-projects:example:jsonnpm run placement-projects:examplenpm run placement-projects:example:jsonnpm run placement-projects:split-example:jsonnpm run stats-projects:examplenpm 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 jsonnode ./src/cli/index.js summarize-projects --from-project-audits ./project-audits.json --format jsonnode ./src/cli/index.js rank-projects --from-project-audits ./project-audits.json --format jsonnode ./src/cli/index.js plan-projects --from-project-audits ./project-audits.json --format jsonnode ./src/cli/index.js findings-projects --from-project-audits ./project-audits.json --format jsonnode ./src/cli/index.js placement-projects --from-project-audits ./project-audits.json --format jsonnode ./src/cli/index.js stats-projects --from-project-audits ./project-audits.json --format json
powershell
npm run audit:examplenpm run audit:kotlin-fixture

Output the structured audit graph:

powershell
npm run audit:example:jsonnpm run audit:kotlin-fixture:json

Generate an actionable test plan from the audit graph:

powershell
npm run plan:examplenpm run plan:example:jsonnpm run hints:examplenpm run hints:example:jsonnpm run plan:kotlin-fixturenpm run plan:kotlin-fixture:jsonnpm run plan:item:examplenpm run plan:changednpm 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.tsnode ./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:examplenpm run placement:example:jsonnpm run placement:from-audit:example

Exercise the MCP-style tool surface:

powershell
npm run mcp:toolsnpm run mcp:analyze:examplenpm run mcp:adaptersnpm run mcp:detect-rulesnpm run mcp:detect:examplenpm run mcp:audit-projects:examplenpm run mcp:summarize-projects:examplenpm run mcp:rank-projects:examplenpm run mcp:plan-projects:examplenpm run mcp:findings-projects:examplenpm run mcp:placement-projects:examplenpm run mcp:placement-split:examplenpm run mcp:stats-projects:examplenpm run mcp:audit:examplenpm run mcp:audit:kotlin-fixturenpm run mcp:placement:examplenpm run mcp:audit:envelopenpm run mcp:stdionpm 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 testnpm run alpha:checknpm run release:check

Find and rank active public repositories for real-world adapter validation:

powershell
npm run validation:repos -- --profile reactnpm run validation:repos -- --profile workspace --limit 10npm 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:checknpm run corpus:scorecardnpm run corpus:measure -- --case python-asyncer --checkout /path/to/pinned/asyncernpm run corpus:measure -- --case python-django --checkout /path/to/pinned/django --profile-phasesnpm run csharp:performance:checknpm run javascript:performance:checknpm run python:performance:checknpm run kotlin:performance:checknpm run rust:performance:checknpm run swift:performance:checknpm run go:performance:checknpm run ruby:performance:checknpm 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:checknpm run eval:summarynpm run eval:testnpm run eval:update

Check model-consistency scenario locked fields against deterministic tool results:

powershell
npm run model-consistency:checknpm run model-consistency:jsonnpm run model-consistency:json -- --profile local-smallnpm run model-consistency:compare -- baseline-summary.json candidate-summary.jsonnpm 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:checknpm run bin:checknpm run installed-package:checknpm run distribution:checknpm 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.jsexamples/  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/

JavaScript/TypeScript, PHP, Python, Ruby, Swift, bounded Kotlin/JVM modules, bounded Go modules, bounded C# SDK project shapes, and bounded Rust Cargo packages are supported adapter proof points. PHP support covers the bounded Composer/PSR-4/PHPUnit ownership, command-withholding, and evidence rules in PHP Alpha Support. Ruby support covers the bounded Bundler/Minitest/RSpec ownership and evidence rules in Ruby Alpha Support. Rust support includes literal repository-contained workspace members, exact package commands, built-in test ownership, literal module graphs, exact test-only module exclusion, direct logical-module imports, inherent associated calls, and exact unconditional crate-root symbol re-exports as defined in Rust Alpha Support. C# support covers one conventional 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 target-conditioned package predicates, and a pair amid unrelated projects, with bounded nearest-file build metadata and static central package versions, exact test-project 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 while solution ownership remains excluded. Go support includes literal repository-contained go.work members, explicit static build-target selection, bounded standard-library/Testify assertion usage, parser-scoped receiver identity through concrete local and test-helper bindings, and callable-body-owned source evidence as defined in Go Alpha Support. Kotlin/JVM support is limited to conventional Gradle/Maven modules and directly declared aggregate graphs, JUnit, the documented Kotest common-spec and Spock feature variants, or method-level TestNG, and standard source sets as defined in Kotlin/JVM Alpha Support.

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

来源:README.md,提交 1f0c0dc

工具

19

analyze_repository

Analyze Repository

Start here for an unfamiliar repository or a general test-architecture review. Detect and audit all project roots once, then return the complete deterministic summary, blockers, findings, ranking, plan, execution hints, verification commands, and stats. Prefer this over audit_repo unless one project root and adapter were explicitly selected.

输入参数goTargetrepoRoot必填changedPathsexcludeProjectRoots

list_adapters

List Adapters

List registered language adapters available to audit repositories.

无需输入参数。

list_project_detection_rules

List Project Detection Rules

List deterministic project marker rules and ignored directories used during project detection.

无需输入参数。

detect_projects

Detect Projects

Discover project roots, support status, and matching adapters without auditing source targets. Use this when project boundaries are needed before a specialized workflow; use analyze_repository for a complete review. Reads local repository markers and returns project-detection/v1 without executing tests or writing files.

输入参数repoRoot必填excludeProjectRoots

audit_projects

Audit Projects

Return raw per-project audit artifacts for all detected supported roots, report unsupported roots, and list roots whose adapter failed in failedProjects. Use when a downstream specialist tool needs project-audits/v1; for a complete first-pass review, prefer analyze_repository.

输入参数goTargetrepoRoot必填changedPathsexcludeProjectRoots

summarize_project_audits

Summarize Project Audits

Summarize an existing project-audits/v1 artifact. Use only when a compact coverage view is needed separately; analyze_repository already includes this result.

输入参数projectAudits必填

rank_project_candidates

Rank Project Test Candidates

Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result.

输入参数projectAudits必填

generate_project_test_plan

Generate Project Test Plan

Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result.

输入参数projectAudits必填

collect_project_findings

Collect Project Findings

Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result.

输入参数projectAudits必填

analyze_project_test_placement

Analyze Project Test Placement

Derive advisory test-placement findings across an existing project-audits/v1 artifact while preserving project identity. Use this for multiple audited projects; use analyze_test_placement for one audit/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.

输入参数projectAudits必填

collect_project_stats

Collect Project Stats

Aggregate coverage, counts, risk and signal distributions, frameworks, and adapter usage from an existing project-audits/v1 artifact. Use this for separate reporting or comparisons; analyze_repository already includes the same stats. Returns project-stats/v1 without rescanning the repository, executing tests, or writing files.

输入参数projectAudits必填

audit_repo

Audit Repository

Audit one explicitly selected project root and return audit/v1. Use only when the caller selected a single adapter or project boundary; adapterId defaults to javascript. For an unfamiliar or complete repository review, use analyze_repository.

输入参数goTargetrepoRoot必填adapterIdchangedPaths

get_audit_graph

Get Audit Graph

Validate and return an existing audit/v1 artifact unchanged; this does not scan a repository. Use audit_repo or analyze_repository for repository discovery.

输入参数audit必填

generate_test_plan

Generate Test Plan

Create a deterministic plan/v1 from an existing single-project audit/v1 artifact. Use this after audit_repo, optionally selecting one exact plan item; use generate_project_test_plan for multiple audited projects. Does not rescan the repository, execute tests, or generate or write test code.

输入参数audit必填itemId

get_plan_execution_hints

Get Plan Execution Hints

Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents.

输入参数plan必填itemId

explain_target

Explain Audit Target

Explain the evidence, risk, testability, and recommendation for one target in an existing audit/v1 artifact. Use this after audit_repo or audit_projects when one target needs detail beyond the audit summary. Returns target-explanation/v1 without rescanning the repository, executing tests, or writing files.

输入参数audit必填targetId必填

rank_test_candidates

Rank Test Candidates

Rank testable audit targets by risk reduction and maintenance cost.

输入参数audit必填

analyze_test_placement

Analyze Test Placement

Derive advisory test-placement findings from an existing single-project audit/v1 artifact. Use this for one audited project; use analyze_project_test_placement for a project-audits/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files.

输入参数audit必填owner

generate_selected_test

Generate Selected Test (Deferred)

Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled.

输入参数planItemId必填

版本历史

4
  1. v1.1.0最新Oct 30, 2026
  2. v1.0.1Oct 29, 2026
  3. v1.0.0Oct 1, 2026
  4. v1.0.0-beta.2Sep 16, 2026

评分

已满足适用检查项的 90%

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

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

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

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分