[curriculum-eval] curriculum_assessment.py: checkpoint_quality — regex misses :white_check_mark: and :clipboard: headings, penalising all pages
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
Research direction
Start with .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, especially CHECKPOINT_RE and the prerequisite and activity:checkpoint detection it uses; inspect any existing unit tests. Update the patterns to recognize both literal emoji and GitHub shortcode headings while preserving ## Prerequisites, then run the assessment over workshop/*.md. Done means matching headings are detected and the false missing_checkpoint flags are cleared; do not edit workshop content.
Written by the indexing model from the issue text.
Description
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 92 of 94 pages | ≥ 4 items → 10 | −10 |
| scaffolding | 5.0 on 94 of 94 pages | 10 when "Before You Start" present | −5 |
Root Cause (≤ 2 sentences):
CHECKPOINT_RE = r"##\s+✅\s*Checkpoint" and the prereq regex ##\s+📋\s*Before You Start match only literal emoji, but workshop files use GitHub shortcodes (## :white_check_mark: Checkpoint, ## :clipboard: Before You Start). Every page loses about 2.0 × 10 (checkpoint) and 1.5 × 5 (scaffolding) weighted points, so scores cluster at 5–7 and the "missing_checkpoint" flag is meaningless.
Evidence (quoted from the file):
CHECKPOINT_RE = re.compile(r"##\s+✅\s*Checkpoint", re.IGNORECASE)(the pageworkshop/side-quest-11-06-anthropic-key.mdhas## :white_check_mark: Checkpointwith 5 checklist items, yethas_checkpointisfalse)
Learning Science Rationale:
Valid measurement is a precondition for acting on Bloom's-aligned assessment and cognitive-load findings: retrieval-practice checkpoints are a key scaffolding feature (Roediger and Karpicke's testing effect), and a rubric that scores them as absent on every page cannot discriminate good from poor steps. The false negatives also hide real gaps and produce spurious trend swings (for example the −2.00 "declines" on side-quest-11-09-agent-session-phases.md and side-quest-12-01-iterate-agent-output.md).
Improvement Prompt (for an agent):
In .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, update CHECKPOINT_RE and the has_prereq_section regexes so they accept both the literal emoji and the GitHub shortcode forms: "## ✅ Checkpoint" / "## :white_check_mark: Checkpoint", and "## 📋 Before You Start" / "## :clipboard: Before You Start" (also keep "## Prerequisites"). Also update the Bloom "activity:checkpoint" detection that uses CHECKPOINT_RE. Add or update unit tests if present, rerun the assessment over workshop/*.md, and confirm has_checkpoint is true for pages with a Checkpoint heading and that the corpus mean rises accordingly. Do not edit workshop content.
Expected Score After Fix: ~7.5 / 10.0 corpus mean (checkpoint_quality and scaffolding recovered on most pages)
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · ~46 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷
- expires on Nov 8, 2026, 3:30 AM UTC
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 40
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5436 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#5434 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5433 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5427 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#5421 ·
Maintainers usually reply within 3 days
All issues in githubnext/gh-aw-workshop
Similar issues
-
stringify escapes leading digits in pseudo-class arguments (:nth-child(1) becomes :nth-child(\31 ))Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
digitalbazaar/forge#1170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-form#664 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jenkinsci/jenkins#27705 · 3 comments ·
Maintainers usually reply within 1 day