Create a fixed JSON evaluation suite from a repository's existing tests and check its structure for errors. Use the suite with harness-evolve to compare variants against consistent tasks, independently of the repository's normal test command.
中文简介正在准备中。当前显示英语简介。
Manage `@metaharness/darwin` bench suites — `bench create {repo}` scaffolds a JSON suite from a repo's test corpus; `bench verify {suite.json}` checks suite well-formedness. Bench suites are the fixed evaluation corpora that `harness-evolve --bench {suite.json}` scores variants against, decoupling evolution from the repo's natural tests. Degrades gracefully when @metaharness/darwin is absent.
安装前可以查看交给 AI 代理的指令内容。
Surfaces metaharness-darwin bench <create|verify> — the supporting verb
for harness-evolve --bench. Use when you want evolution scored against a
fixed corpus (independent of npm test) so champion fitness is comparable
across commits or across forks of the same harness.
npm test is
flaky, slow, or undersized — scaffold a deterministic bench suite once,
then evolve against it repeatedly.bench verify the checked-in suite on every PR that touches it
(cheap; ~5s).Implementation: scripts/bench.mjs.
--op create--repo path; reject if missing.metaharness-darwin bench create <repo> [--out <suite.json>].<repo>/.metaharness/bench/suite.json (chosen by upstream).{ input, expectedOutput, weight } tasks
derived from existing test cases.--op verify--suite path; reject if missing.metaharness-darwin bench verify <suite.json>.{
"success": true,
"data": {
"op": "verify",
"taskCount": 42,
"wellFormed": true,
"durationMs": 870
}
}
| Code | Meaning |
|---|---|
| 0 | OK (or degraded — Darwin absent) |
| 1 | --op verify and suite malformed |
| 2 | Config error or upstream invocation failure |
When @metaharness/darwin is absent, emits the standard {degraded: true, reason: 'metaharness-darwin-not-available'} payload and exits 0.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
中文简介正在准备中。当前显示英语简介。
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
中文简介正在准备中。当前显示英语简介。
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
中文简介正在准备中。当前显示英语简介。
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
中文简介正在准备中。当前显示英语简介。
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
中文简介正在准备中。当前显示英语简介。
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.
中文简介正在准备中。当前显示英语简介。