feat(agents): PreToolUse nudges for the remaining harnesses, and Hermes skill support

Aperta
#116 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
Più di una settimana
Idoneità per principianti
22/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli, devtools

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:agents feature priority:low spec-needed
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

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Lingua principale
Go
Stelle
0
Fork
0
Merge medio
7h 42m
PR unite (30g)
111

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di seanb4t/codegraph-go

Tutte le issue di seanb4t/codegraph-go

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.