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

Abierto Apto para principiantes
  • ¿Algo no está bien?
#5,699 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown, python
Área
tooling

Línea de trabajo

Empieza en .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, donde CHECKPOINT_RE y la expresión regular de Before You Start solo coinciden con los encabezados de emoji. Amplía ambos patrones para que también acepten los shortcodes :white_check_mark: y :clipboard:, manteniendo la alternativa de Prerequisites. Actualiza los fixtures que haya en ese directorio del skill y luego confirma que workshop/side-quest-17-07-repo-poisoning.md devuelve has_checkpoint=true.

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

Descripción

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
Lenguaje dominante
JavaScript
Estrellas
62
Forks
43
Merge medio
11 h 26 min
PR fusionados (30 d)
13

Preparar el entorno

Abrir en Codespaces

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

  • Sin Dockerfile ni archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

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

Todos los issues de githubnext/gh-aw-workshop

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.