Hooks at named sections inside a command, not only before and after it

Abierto
#5,340 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
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown, python
Área
tooling

Línea de trabajo

Start by reading the core command templates and the existing hook implementation; the issue does not name specific files or tests. Trace how hooks run before and after whole steps, then check how section markers could identify hook points within a command. Done means hooks can run before or after named sections while existing commands and hooks without section names continue to work.

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

Descripción

triage-nice-to-have

Hooks today run before or after a whole step (before_plan, after_tasks). There is no way to run something in the middle of a step, such as after the plan's design and before its constitution check, without forking the command file.

Proposal

  • Mark named sections in the core command templates, for example <!-- section: design -->.
  • Let a hook name a section: before: plan.design or after: tasks.generate.
  • Commands with no marked sections, and hooks with no section, work exactly as they do now.

Why
A team that wants one extra check at one point has to copy the whole command today, and the copy misses every upstream change. We run this model in the SpecKit Companion extension (named nodes plus hooks before or after any of them), and it has removed most of our reasons to fork a command.

Related: #2047.

AI disclosure: drafted with Claude Code (Claude Opus 5.5, default settings); I checked it before posting.

Lenguaje dominante
Python
Estrellas
149k
Forks
13.4k
Merge medio
1 d 5 h
PR fusionados (30 d)
223

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 github/spec-kit

Todos los issues de github/spec-kit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.