Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

fix: vendored skills' drift-check scripts disagree on what their exit codes mean

Abierto
  • ¿Algo no está bien?
#6,493 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, shell
Área
ci-cd, tooling

Línea de trabajo

Start with the six vendored skills' scripts/update.sh (playwright, firecrawl, playbooks/boris, playbooks/skill-authoring, dometrain sync, context7 lookup) and map each script's current exit paths onto the proposed contract: 0 no drift, 1 upstream drift, 2 unverifiable. Then look at firecrawl's --check baseline-reading step to find why a missing CLI counts as drift and why the report shows last sync: recorded). Done means every script returns the shared codes with a test pinning each code, and the maintenance-check-upstream-drift workflow matrix (issue #6477) uses one drift rule for all rows.

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

Descripción

needs-triage

Problem

The six vendored skills' scripts/update.sh drift checks each define their own exit codes, so nothing can read them the same way:

Script Exit 1 Exit 2 Drift
playwright, firecrawl, playbooks boris, playbooks skill-authoring drift prerequisite or network failure exit 1
dometrain sync prerequisite missing or unverifiable drift exit 2
context7 lookup prerequisite missing unverifiable exit 0, reported only on stdout

Two more quirks found on 2026-10-07:

  • firecrawl's --check counts a CLI that is not installed as drift, so it exits 1 on any machine without the CLI, whether upstream moved or not.
  • firecrawl's report printed last sync: recorded) and recorded SHA256: recorded), which looks like its baseline-reading step picks up the wrong field.

The weekly maintenance-check-upstream-drift workflow (melodic-software/claude-code-plugins#6477) works around all of this with a per-row drift rule, which is fragile.

Proposed

One exit-code contract for every vendored drift check: 0 no drift, 1 upstream drift, 2 unverifiable (prerequisite or network). A missing local CLI is reported but is not upstream drift. Fix the firecrawl baseline read. Then simplify the workflow's matrix to the shared contract.

Acceptance

  • All six scripts follow the shared contract, each with a test that pins it.
  • The workflow's matrix uses one drift rule for every row.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 25 min
PR fusionados (30 d)
944

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.