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

Abierto
#116 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
cli, devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
7 h 42 min
PR fusionados (30 d)
111

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de seanb4t/codegraph-go

Todos los issues de seanb4t/codegraph-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.