feat(agents): PreToolUse nudges for the remaining harnesses, and Hermes skill support
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with the existing opt-in nudge in internal/nudge, which covers Claude Code and Codex, and with internal/agents/hermes.go, which currently writes only MCP config. Each harness first needs its hook mechanism verified against primary docs or a live session, so the first step is a verification note per item, not code. Done means each harness either has a capability-table-driven nudge with a recorded live session, or the item is closed as not possible with the evidence attached.
由索引模型根据 Issue 内容生成。
描述
What problem does this solve?
The opt-in PreToolUse nudge exists only for Claude Code and Codex. Hermes receives an MCP entry only: no skill and no hooks.
What should it do?
Each item first needs the harness's mechanism verified against primary docs or a live session:
- NUDGE-07 Cursor (
.cursor/hooks.json; the non-blocking output shape is unverified) - NUDGE-08 Kiro (
.kiro/hooks/<id>.json,{"type":"agent"}) - NUDGE-09 Gemini CLI (
.gemini/hooks/) - NUDGE-10 opencode, Antigravity (mechanisms
[ASSUMED]) - AGENT-12 Hermes skill and hooks (no public docs found)
- Codex SessionStart nudge; Codex skill metadata (
agents/openai.yaml) and plugin packaging
Which surface does this affect?
Other (agent install)
Is this covered by an existing command or tool today?
Partly. codegraph install --pretool-nudge covers Claude Code and Codex (internal/nudge). internal/agents/hermes.go writes MCP config only.
Acceptance criteria
- Each harness either gets a nudge driven by the capability table, with a live-session record, or the item is closed as not possible, with the evidence.
Source (GSD planning files, archived at d384473e): .planning/milestones/v0.14.0-REQUIREMENTS.md (v2: NUDGE-07…10, AGENT-12); .planning/ROADMAP.md (Later); .planning/milestones/v0.14.0-phases/07-codex-parity/07-CONTEXT.md (Deferred Ideas)
🤖 Generated with Claude Code
- 主要语言
- Go
- 星标
- 0
- 派生
- 0
- 平均合并
- 7 小时 42 分钟
- 30 天内合并 PR
- 111
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
seanb4t/codegraph-go 的其他 Issue
-
chore needs-triage
难度 1/5 1 小时以内 新手友好度 88/100
seanb4t/codegraph-go#380 ·
维护者通常 1 天内回复
-
chore needs-triage
难度 2/5 1-3 小时 新手友好度 82/100
seanb4t/codegraph-go#379 ·
维护者通常 1 天内回复
-
area:query chore needs-triage spec-needed
难度 2/5 1-3 小时 新手友好度 74/100
seanb4t/codegraph-go#377 ·
维护者通常 1 天内回复
-
chore needs-triage
难度 1/5 1-3 小时 新手友好度 84/100
seanb4t/codegraph-go#362 ·
维护者通常 1 天内回复
-
area:query bug needs-triage
难度 2/5 1-3 小时 新手友好度 80/100
seanb4t/codegraph-go#355 ·
维护者通常 1 天内回复
查看 seanb4t/codegraph-go 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
v2fly/domain-list-community#4307 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
notify: voice_queue rows are deleted only at startup, so a hub that stays up grows it without bound未关闭
难度 2/5 1-3 小时 新手友好度 72/100
mattabate/life-distributable#232 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 86/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 83/100
维护者通常 1 天内回复