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 in a single page

Closed Beginner friendly
#5,037 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
82/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 the issue’s improvement prompt. Tighten the attack and rationale sections, then reduce concept overload by moving code samples into <details> blocks or pairing each defence with a short exercise. Keep the preparation section and a checkpoint with at least four specific items; aim for no more than 900 words and 15 new concepts, then run the stated markdownlint command.

Written by the indexing model from the issue text.

Description

curriculum documentation quality

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

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 5.8 (1234 words) ≤ 800 words, ≤ 15 concepts −434 words; concept_overload flagged
active_learning 2.7 density ≥ 3 −0.3
checkpoint_quality 0.0 (rubric false negative; page has a 6-item checkpoint) ≥ 4 items see rubric issue

Root Cause (≤ 2 sentences):
The page covers the attack, why it matters, four-plus defences (contents: read, safe-outputs, protected-files, network.allowed-domains) and two exercises in one sitting. This overloads working memory and sets the lowest score in Part 2.

Evidence (quoted from the file):

I can name the two gh-aw features (contents: read and safe-outputs: create-pull-request) that remove the direct-commit path

Learning Science Rationale:
Cognitive Load Theory (Sweller) holds that novices can process only a few new elements at once; worked-example research suggests introducing one defence, then letting learners apply it, before the next. Splitting the defences section from the exercises (segmenting, per Mayer) reduces extraneous load and lets each exercise directly follow the concept it practises.

Improvement Prompt (for an agent):

Edit workshop/side-quest-17-07-repo-poisoning.md. Reduce to ≤ 900 words and ≤ 15 new concepts: tighten "The Attack" and "Why This Matters", move the long "How AW Defends Against It" code samples into <details> blocks or interleave each defence with a one-step exercise, and remove duplicate explanations. Keep ":clipboard: Before You Start" and the "## :white_check_mark: Checkpoint" with ≥ 4 specific items. Do not number headings. Run `npx --yes markdownlint-cli2 "**/*.md"`.

Expected Score After Fix: 7.5 / 10.0 (after the checkpoint regex is also fixed)

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

  • expires on Oct 28, 2026, 6:06 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.