Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#6,493 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
70/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
github-actions, shell
Ambito
ci-cd, tooling

Direzione di ricerca

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.

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

Descrizione

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.
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
5h 4m
PR unite (30g)
825

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

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.