[curriculum-eval] curriculum_assessment.py: checkpoint_quality — regexes miss `:white_check_mark:`/`:clipboard:` headings, scoring 93 pages as mis

Aperta Adatta ai principianti
  • Qualcosa non va?
#5,699 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
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown, python
Ambito
tooling

Direzione di ricerca

Inizia da .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, dove CHECKPOINT_RE e la regex di Before You Start corrispondono solo alle intestazioni con emoji. Amplia entrambi i pattern in modo che accettino anche gli shortcode :white_check_mark: e :clipboard:, mantenendo l'alternativa Prerequisites. Aggiorna le fixture presenti in quella directory dello skill, quindi conferma che workshop/side-quest-17-07-repo-poisoning.md restituisce has_checkpoint=true.

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

Descrizione

curriculum documentation quality

File: .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py
Overall Score: corpus mean 6.06 / 10.0 (threshold 5.52)

Flagged Dimensions:

Dimension Score Benchmark Delta
checkpoint_quality 0.0 on 93/95 pages (has_checkpoint true for only 2) present, ≥ 4 items → 10 −10.0
scaffolding 5.0 on 95/95 pages (has_prereq_section true for 0) "Before You Start" present → 10 −5.0

Root Cause (≤ 2 sentences):
CHECKPOINT_RE matches only the literal ## ✅ Checkpoint and the scaffolding regex only ## 📋 Before You Start, but workshop pages use the GitHub shortcodes ## :white_check_mark: Checkpoint and ## :clipboard: Before You Start. As a result nearly every page loses 20 weighted points of checkpoint score and 5 of scaffolding.

Evidence (quoted from the file):

CHECKPOINT_RE = re.compile(r"##\s+✅\s*Checkpoint", re.IGNORECASE) ... re.search(r"##\s+📋\s*Before You Start", raw, re.IGNORECASE)

versus workshop/side-quest-17-07-repo-poisoning.md line 191: ## :white_check_mark: Checkpoint followed by 6 checklist items (scored checkpoint_quality 0.0).

Learning Science Rationale:
Valid measurement is a precondition for applying any framework. Retrieval practice and formative-assessment research (Roediger & Karpicke) supports checkpoints as a key learning feature, and the rubric is meant to reward them. A detector that cannot see them yields systematically misleading scores, hides real gaps (pages that truly lack checkpoints) and misdirects remediation effort onto already-compliant pages.

Improvement Prompt (for an agent):

In .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, update CHECKPOINT_RE to match both "## ✅ Checkpoint" and "## :white_check_mark: Checkpoint" (e.g. r"##\s+(?:✅|:white_check_mark:)\s*Checkpoint"), and update the has_prereq_section regex to match both "## 📋 Before You Start" and "## :clipboard: Before You Start" (keep the "## Prerequisites" alternative). Update any tests/fixtures under .github/skills/curriculum-quantitative-assessment/, re-run the assessment over workshop/*.md, and confirm that pages such as workshop/side-quest-17-07-repo-poisoning.md now report has_checkpoint=true. Report the new corpus mean and list any pages that still genuinely lack a checkpoint.

Expected Score After Fix: ~8.0 / 10.0 corpus mean (estimated: +2.0 from checkpoints, +0.35 from scaffolding for most pages)

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · ~46 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷

  • expires on Nov 15, 2026, 3:31 AM UTC
Lingua principale
JavaScript
Stelle
62
Fork
43
Merge medio
12h 23m
PR unite (30g)
12

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

  • Nessun Dockerfile né file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 githubnext/gh-aw-workshop

Tutte le issue di githubnext/gh-aw-workshop

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.