Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[curriculum-eval] curriculum_assessment.py: checkpoint_quality — regex misses :white_check_mark: and :clipboard: shortcodes, mis-scoring 92/94 pag

Open Beginner friendly
  • Is something wrong?
#5,067 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python
Domain
content, testing-qa

Research direction

Read .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, especially CHECKPOINT_RE, the prerequisite check, and checklist_items. Compare those patterns with headings in workshop/04-github-actions-intro.md; then inspect the related unit tests. Done when both emoji and shortcode heading forms are recognized and the assessment reports checkpoints on pages that contain them.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

File: .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py
Overall Score: n/a — affects all 94 pages (corpus mean: 6.06)

Flagged Dimensions:

Dimension Score Benchmark Delta
checkpoint_quality 0.0 on 92/94 pages ≥ 10 when ≥ 4 items −10
scaffolding 5.0 on 94/94 pages 10 when section present −5

Root Cause (≤ 2 sentences):
CHECKPOINT_RE is ##\s+✅\s*Checkpoint and the prereq check uses ##\s+📋\s*Before You Start, but workshop files use the GitHub shortcodes :white_check_mark: and :clipboard:. Metrics show has_checkpoint=true on only 2 pages and has_prereq_section=true on 0, while pages such as 04-github-actions-intro.md have both sections.

Evidence (quoted from the file):

## :white_check_mark: Checkpoint ... - [ ] You can identify on, jobs, and steps in a workflow file (from workshop/04-github-actions-intro.md, flagged missing_checkpoint)

Learning Science Rationale:
A measurement instrument must be valid before its output guides instruction: a systematic false negative on checkpoints (retrieval-practice and formative-assessment prompts, which Bloom-style mastery learning relies on) misdirects authors toward fixing non-problems and hides real gaps. It also distorts trend data — side-quest-11-09-agent-session-phases.md and side-quest-12-01-iterate-agent-output.md each dropped exactly 2.00 (the checkpoint weight) in the history window, consistent with a heading-format change rather than a content change.

Improvement Prompt (for an agent):

In .github/skills/curriculum-quantitative-assessment/curriculum_assessment.py, update CHECKPOINT_RE to match both the emoji and the shortcode heading forms, e.g. r"##\s+(?:✅|:white_check_mark:)\s*Checkpoint", and update the has_prereq_section regex to accept "##\s+(?:📋|:clipboard:)\s*Before You Start" as well as "##\s+Prerequisites". Check how checklist_items is counted so it also works for the shortcode form. Add/extend unit tests covering both forms, then re-run the assessment against workshop/ and confirm has_checkpoint is true for every page that contains a Checkpoint heading (all except 00-welcome, 01-prerequisites, 06-install-gh-aw, README) and that the corpus mean rises by about 2 points.

Expected Score After Fix: ~8.0 / 10.0 corpus mean (from 6.06; +2.0 checkpoint, up to +0.75 scaffolding)

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

  • expires on Oct 29, 2026, 3:35 AM UTC
Dominant language
JavaScript
Stars
56
Forks
40
Avg merge
2d 7h
Merged PRs (30d)
16

Getting set up

Open in Codespaces

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.