Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

test(planning): run the seven interview eval-first cases and land the rules whose case fails

未关闭
#7,269 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
github, shell
领域
testing-qa

调研方向

Start with the /evals:plugin-eval Cost guidance and inspect PR #7247 to identify the seven eval cases. Run cases one or two at a time against a copy of plugins/planning outside git, then use run-validity.py and noise-report.py to review valid results; inspect kept traces for the two cases that prohibit Bash. Done means rules are added to the interview skill's context spokes only for cases that fail on main, with each change citing its result.

由索引模型根据 Issue 内容生成。

描述

needs-triage

Summary

PR #7247 adds seven eval-first cases for /planning:interview behaviors, a to g: read-back of a dictated answer, active-reply final confirmation, changes-only final brief, a checkable basis and flip condition on each recommendation, the "something else" closing probe, a MoSCoW Must-test scope cut before /planning:wayfind, and one crux question on a rejected recommendation. Under Instruction economy, the rule for each case lands only if its case fails on main.

State

  • All seven llm judges were calibrated against an opus judge at 100% agreement.
  • The first full pass stopped at its cost ceiling (partial: true). Five cases finished, interview-recommendation-basis-and-flip finished partly, and interview-scope-cut-moscow did not run. Under the plugin-eval reading rules, a partial run's scores are not comparable, so they are not used.
  • Per-run cost came out well above the fresh-suite headroom estimate. Size the next pass from that pass's own costUsd (see /evals:plugin-eval, Cost).

Fix

  1. Run the cases one or two at a time (--case <name>, --runs 3, --judge-model opus, --keep-temp) on a copy of plugins/planning outside git, because the repository has too many linked worktrees for the CLI to screen.
  2. Read each result with run-validity.py and noise-report.py. For final-confirm-active-reply and final-brief-changes-only, read the kept traces: those cases allow no Bash, so the Step 3 register-gate script cannot run in them.
  3. For each case that fails on main, add its rule to the interview skill's context spokes in a PR that cites the result.

Related

  • #7247
  • #6986 and #7036 (the eval-first precedent)
主要语言
Shell
星标
22
派生
2
平均合并
7 小时 42 分钟
30 天内合并 PR
923

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。