feat(framework): support portable multi-host skill evaluation

未關閉
#1,237 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
22/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript

研究方向

Start with scripts/skill-eval.mjs, where the Claude-only launch, skill staging under .claude/skills/, judge handling and PASS/FAIL reporting live, and with scripts/skill-eval/cases.json and its README for the fixtures. Read the archived multi-host branch only for reference. Done means the default Claude invocation still passes its existing cases, --host=codex works with a deterministic fake-CLI test, and invalid --jobs or --repeat values fail before any host runs. The scope spans several subsystems and needs a design decision first, so it is not a good first task.

由索引模型根據 Issue 內容生成。

描述

Problem

The existing scripts/skill-eval.mjs runner is Claude Code-specific: it launches claude -p and stages skills under .claude/skills/. This prevents contributors using Codex CLI from running the same applicable behavioral evaluation cases through their native host.

The current harness also has no explicit INCOMPLETE outcome: skipped judge checks are marked ok: true, and case results are reported as PASS or FAIL. It parses --jobs and --repeat as numbers without validating positive integer values before launching hosts.

Earlier work in #992 added Codex execution, JSON assertions, filesystem snapshots, and explicit incomplete-result reporting; those unrelated changes were removed to keep #992 focused on Kilo-native generation following maintainer feedback. The historical implementation is preserved under a tag on the contributor's fork.

The need is distinct from #1079 (what constitutes trustworthy skill-behavior evidence) and #1236 (portable contributor AI resources). Without coordinated boundaries, these efforts could duplicate host launchers and skill-discovery test harnesses.

Scope

  • Extend the existing runner with --host=claude|codex, retaining Claude as the default and keeping existing cases compatible.
  • Introduce a minimal host-adapter boundary for native CLI execution, skill staging and discovery in isolated temporary projects, exit/error capture, and host/version/model metadata where available.
  • Keep portable cases and deterministic assertions independent of host adapters; explicitly report unsupported host features rather than silently skipping them.
  • Add a deterministic jsonValid assertion and optional before/after project-tree snapshots to detect unexpected mutations, without following symlinks outside the isolated workspace.
  • Define PASS, FAIL, and INCOMPLETE with distinct failure diagnostics. Skipped optional LLM-judge checks must not make otherwise complete deterministic evaluations incomplete; skipped required evidence must never produce a full PASS.
  • Validate positive integer --jobs and --repeat arguments before any host invocation.
  • Reuse skill-eval as the preferred behavioral execution infrastructure for the contributor skills investigated in #1236 where applicable; avoid a second independent host-execution or skill-discovery harness unless a concrete limitation is demonstrated. The runner must remain usable without aidd-contributor.
  • Maintain the boundary with #1079: this issue builds execution/assertion facilities, not an evidence protocol, grading methodology, or proof of complete skill compliance.
  • Start from current next; inspect the archived historical implementation (commit ccd32e3bd9075cce43be6bea4a7bb1c60a14e6dd) and port selectively, rather than cherry-picking unrelated changes from #992.
  • Keep model-backed evaluations local and opt-in. Deterministic runner tests may run in CI without authentication or paid-model calls. Design for later Kilo/OpenCode adapters without implementing them in this issue.

Acceptance criteria

  • Existing Claude evaluation cases and default invocation remain compatible, with regression tests.
  • One applicable evaluation fixture is exercised with both Claude Code and Codex CLI; report the observed host versions, commands, and outcomes (or explicitly document any unavailable runtime validation).
  • A deterministic fake-CLI test exercises each host adapter without model credentials and verifies skill staging, invocation, output, and error capture.
  • Unsupported host selection and capabilities produce explicit diagnostics; portable assertions do not contain host-specific launch logic.
  • Valid JSON passes jsonValid; malformed JSON fails it in isolated tests.
  • Snapshot tests detect creation, modification, and deletion while refusing to traverse external symlink targets.
  • Tested result classification distinguishes failed assertions, failed host invocation, unavailable required evidence, and omitted optional judge checks.
  • Invalid, zero, negative, and non-integer --jobs or --repeat values fail before host execution.
  • A documented contributor-skill example demonstrates how the #1236 POC could reuse the runner, without requiring an aidd-contributor installation or introducing a parallel harness.
  • Documentation explicitly separates this runner from the evidence methodology proposed in #1079.
  • No mandatory authenticated model-backed CI execution is introduced.

Prior art in this repo

Out of scope

  • Implementing an aidd-contributor plugin or distributing contributor instructions/rules/hooks (investigated by #1236).
  • Defining or replacing the behavioral evidence protocol and grading semantics of #1079.
  • Implementing Kilo Code, OpenCode, or every supported host in the initial change.
  • Benchmarking or ranking language models.
  • Introducing mandatory authenticated AI-backed CI gates.
  • Rewriting production skills, altering canonical plugin formats, or reintroducing unrelated Project Memory, hook, or generation changes from #992.
主要語言
TypeScript
星號
481
分支
45
平均合併
1 天 13 小時
30 天內合併 PR
91

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。