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

harness-config(audit-instructions): I21 high-pin exemption should key to the model and effort a subagent actually runs at

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
tooling

调研方向

Start with row I21 in plugins/harness-config/skills/audit-instructions/reference/criteria.md, then eval case 34 (i21-high-pin-keys-to-resolved-target-default). The open question is whether the exemption should key to the subagent's model and definition effort instead of the session target; a maintainer needs to decide that first. If yes, done means I21 is updated and case 34 gains a subagent-on-a-different-model variant that passes.

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

描述

needs-triage

Problem

Row I21 in plugins/harness-config/skills/audit-instructions/reference/criteria.md exempts a durable high effort pin when high is the resolved target's default, treating it as equivalent to omitting the level. For an instruction that pins subagents (for example "run every subagent at high effort"), the session's resolved model is not necessarily the model or effort the subagent runs at: a subagent can run on a different model than the session, or at an effort level set in its own agent definition. So a high pin can be a real, unmeasured setting even when the session target defaults to high, and the exemption would hide it.

Evidence

Eval case 34 (i21-high-pin-keys-to-resolved-target-default, added in #6931) was run by hand once against the PR head and once against origin/main. Both runs independently reported this gap while correctly applying the current row.

Question to decide

Should I21's exemption key to the model and effort the pinned surface actually runs at (the subagent's model and its definition's effort, when the pin targets subagents), rather than only the session's resolved target? If so, extend case 34 with a subagent-on-a-different-model variant.

Pointers

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