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

[curriculum-eval] side-quest-17-07-repo-poisoning.md: cognitive_load — 1234 words and concept overload

Open Beginner friendly
#5,104 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
77/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, markdown

Research direction

Read workshop/side-quest-17-07-repo-poisoning.md and revise the lesson using the specific edits in the improvement prompt: shorten the opening sections, condense the four defences, and merge the exercises. Keep “Before You Start” and the checkpoint with at least four verifiable items. Then run npx --yes markdownlint-cli2 "**/*.md"; done means the lesson is at most 900 words and the Markdown lint check passes.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

File: workshop/side-quest-17-07-repo-poisoning.md
Overall Score: 5.0 / 10.0 (corpus mean: 6.1)

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 5.8 ≤ 800 words, ≤ 15 concepts (1234 words) −4.2
active_learning 2.7 density ≥ 3 −7.3

The missing_checkpoint flag is a false positive: the page has a checkpoint at line 191 (see the companion rubric issue).

Root Cause (≤ 2 sentences):
The page teaches the attack, four separate defences (read-only permissions, PR-routed writes, path restrictions, network limits), two exercises and a closing author checklist in a single file. The defences are each explained with prose, and the two exercises do not start until about line 125.

Evidence (quoted from the file):

### Declare read-only permissions / ### Route writes through a pull request / ### Restrict which paths can change / ### Limit network destinations

Learning Science Rationale:
Cognitive Load Theory (Sweller) warns that long expository sequences before any practice overload working memory, and the worked-example/completion effect suggests interleaving each concept with a short task. Moving the practice next to each defence lets the learner apply it immediately, which raises both retention and activity density.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md to reduce cognitive load. Target ≤ 900 words. (1) Shorten "The Attack" and "Why This Matters" to one short paragraph each. (2) Keep the four defences but cut each to a brief explanation plus one frontmatter snippet. (3) Merge the two exercises into one that asks the learner to spot the dangerous frontmatter and then fix it, with an answer in a <details> block. (4) Keep "Before You Start" and the "## :white_check_mark: Checkpoint" section with ≥ 4 specific, verifiable items. Do not number headings and keep callouts ≤ 3. Run `npx --yes markdownlint-cli2 "**/*.md"` and fix any errors.

Expected Score After Fix: 6.5 / 10.0 (before the rubric fix; higher once checkpoint detection is corrected)

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

  • expires on Oct 30, 2026, 4:05 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.