test(cli): per-tool hook fixtures on the latest tool versions

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

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
github-actions, typescript
領域
ci-cd, testing

研究方向

Start by reading #978 for the compatibility results format, then inspect #1191, #1193, and #1194 for tool specific hook failures. Define non-interactive fixtures for each tool and hook moment, and run them weekly against each tool’s latest version in CI. Done means a breaking hook fails the job and every result records the tool version and date.

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

描述

Problem

Tools change fast: agy went from 1.5.1 to 1.5.5 and Cursor updated itself during one afternoon of tests (2026-11-11). Nothing checks that a hook still fires and reaches the model on each tool. Findings so far came from manual runs, one run per case, on small models.

Scope
  • One non-interactive fixture per tool and per moment: does it fire, does it reach the model, can it block or re-prompt.
  • Run on the latest version of each tool, weekly in CI.
  • Results feed COMPATIBILITY.md (#978).
Acceptance criteria
  • A tool update that breaks a hook moment fails the job.
  • Each result states the tool version and the date.
Prior art in this repo
  • #978 (verified compatibility), #1191 (opencode run loses the Stop continuation), #1193, #1194.
Out of scope

Interactive (TUI) modes. Fixtures before the CLI hooks capability exists.

主要語言
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 摘要。