docs(framework): hooks documentation, tool-internal vs pre-commit
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Tranquilo
- Stack tecnológico
- git, javascript
- Área
- documentation
Línea de trabajo
Start with the bundled-hooks section in docs/ARCHITECTURE.md, then review docs/CREATE_PLUGIN.md and docs/GLOSSARY.md alongside the documented Context, Telemetry, OpenCode, and Claude Code hook references. Update the three named documents so the authoring contract, lifecycle and host coverage, and agent-hook versus Git pre-commit boundary are explicit, and confirm every acceptance criterion is met.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
The framework ships bundled hooks, but authors lack one documented, host-aware contract for adding a hook.
Scope
- Extend the existing bundled-hooks section in
docs/ARCHITECTURE.mdwith the minimal hook contract, supported lifecycle mapping, and the boundary with Git hooks. - Link that section from
docs/CREATE_PLUGIN.md. - Correct
docs/GLOSSARY.md: Git pre-commit is not an agent lifecycle event.
Acceptance criteria
- An author can add a basic hook from
ARCHITECTURE.mdwithout reading an existing implementation. - Supported lifecycle events and per-host coverage are explicit.
- The agent-hook versus Git-pre-commit boundary is explicit.
-
CREATE_PLUGIN.mdlinks to the authoritative section. - The glossary no longer classifies pre-commit as an agent lifecycle event.
Prior art in this repo
ARCHITECTURE.mdalready inventories Context and Telemetry hooks, but does not define an authoring contract.- Context and Telemetry have declarative hooks; OpenCode uses a JavaScript plugin bridge.
- Claude Code Hooks documents more events than AIDD currently normalizes.
Out of scope
- Changing or adding a bundled hook.
- Installing Git pre-commit hooks or adding CI enforcement.
- Claiming lifecycle parity that a host has not demonstrated.
- Lenguaje dominante
- TypeScript
- Estrellas
- 481
- Forks
- 45
- Merge medio
- 19 h 38 min
- PR fusionados (30 d)
- 108
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de ai-driven-dev/framework
-
refactor(aidd-orchestrator): the check zone says when to stop, and reviews its axes in one round Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ai-driven-dev/framework#887 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
ai-driven-dev/framework#873 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
ai-driven-dev/framework#872 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
ai-driven-dev/framework#625 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
ai-driven-dev/framework#467 · 1 comentario ·
Todos los issues de ai-driven-dev/framework
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mksglu/context-mode#1200 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anthropics/claude-code#96687 ·
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
AOSSIE-Org/DebateAI#582 · 2 comentarios ·