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

[deep-report] Fix stale pkg/workflow/js/ references in 4 skill files (3rd recurrence, count growing)

Aperta Adatta ai principianti
  • Qualcosa non va?
#64,065 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à
2/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
84/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, markdown
Ambito
documentation, testing-qa

Direzione di ricerca

Inizia cercando nei quattro file indicati sotto .github/skills/ tutti i riferimenti a pkg/workflow/js/, quindi verifica i percorsi corrispondenti sotto actions/setup/js/. Sostituisci i 22 riferimenti obsoleti e aggiorna i nomi dei file di esempio, quindi aggiungi il test Go leggero o lo script richiesto ed eseguilo per confermare che non rimangano percorsi pkg/workflow/js/*.cjs inesistenti.

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

Descrizione

automation code-quality cookie improvement quick-win task-mining
Description

Four .github/skills/ files still contain 22 literal pkg/workflow/js/ path references pointing at a directory that was emptied by the actions/setup/js/ migration back on 2026-08-31. This is the third consecutive audit to catch this (2026-08-31 original, 2026-09-16 follow-up, 2026-09-28 today) and the count has grown (20→22), confirming intervening edits keep re-introducing the stale path rather than fixing it.

Verified live on disk today:

  • pkg/workflow/js/ contains only 2 unrelated files (exchange_otlp_workload_identity.cjs, safe_outputs_tools.json)
  • actions/setup/js/ (the real shared JS location) holds 862 .cjs files including all referenced modules
Affected files and exact fixes
  • .github/skills/messages/SKILL.md (8 refs) — lines 20, 72, 109, 142, 150, 184, 185, 197. Worst offender: line 72 tells agents to create new modules "typically in pkg/workflow/js/"; line 109 gives a concrete non-existent example test path pkg/workflow/js/messages_my_new.test.cjs.
  • .github/skills/javascript-refactoring/SKILL.md (6 refs) — lines 15, 58, 101, 154, 197, 237.
  • .github/skills/error-pattern-safety/SKILL.md (1 ref) — line 102.
  • .github/skills/temporary-id-safe-output/SKILL.md (1 ref) — line 101.

Fix: replace all 22 pkg/workflow/js/ occurrences with actions/setup/js/ (dropping it as a listed alternative where both paths are currently given), and update the example file names to real paths under actions/setup/js/.

Expected Impact

Stops misleading Copilot/Claude agents into creating new JS modules or test files in the wrong, unbuilt directory whenever they consult these 4 high-traffic "how do I edit safe-output JS" skills. Also add a lightweight regression guard (Go test or script) that fails if any .github/skills/**/SKILL.md references a pkg/workflow/js/*.cjs path that doesn't exist on disk, so this class of drift — now reported 3 times — can't silently resurface a 4th time.

Suggested Agent

Repository Quality Improvement workflow (already owns this audit lineage) or any general code-quality agent — this is a mechanical find/replace plus one new test.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing 2026-09-28 (~18:00Z incremental cycle), sourced from discussion #64013 ("Repository Quality Improvement Report - Skill Documentation Drift, Third Audit"). Verified independently against current main before filing.

Generated by 🔬 Deep Report · claude · agent · 198.5 AIC · ⌖ 8.81 AIC · ⊞ 13K · ◷

  • expires on Sep 30, 2026, 10:48 AM UTC-08:00
Lingua principale
Go
Stelle
5.2k
Fork
547
Merge medio
5h 53m
PR unite (30g)
647

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 github/gh-aw

Tutte le issue di github/gh-aw

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.