[curriculum-eval] side-quest-01-02-environment-reference.md: cognitive_load — 1,536 words with low activity density
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 82/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- markdown
调研方向
打开 workshop/side-quest-01-02-environment-reference.md 并从头到尾阅读,注意术语表、checkpoint 部分以及第 83–195 行的“Conceptual screenshots”块。把该屏幕截图部分移到新的 side-quest-01-04-environment-screenshots.md 中,从主页链接到它,添加一个简短的“Try it”块,运行 gh --version、git --version 和 gh auth status,然后将新文件添加到 workshop/README.md。完成意味着主页少于约 800 词,现有标题保持不变且不编号,并且 npx --yes markdownlint-cli2 "**/*.md" 通过。
由索引模型根据 Issue 内容生成。
描述
File: workshop/side-quest-01-02-environment-reference.md
Overall Score: 4.8 / 10.0 (corpus mean: 6.1)
Flagged Dimensions:
| Dimension | Score | Benchmark | Delta |
|---|---|---|---|
| cognitive_load | 5.3 | ≥ 9 (≤ 800 words, ≤ 15 concepts) | −3.7 (1,536 words, 19 concepts) |
| active_learning | 2.4 | ≥ 10 (density ≥ 3) | −7.6 (density 0.72) |
(Note: checkpoint_quality 0.0 and scaffolding 5.0 are scorer false positives; the page has both :white_check_mark: Checkpoint and :clipboard: Before You Start sections. See the scorer-regex issue.)
Root Cause (≤ 2 sentences):
A glossary table plus a long "Conceptual screenshots" section (lines 83–195) roughly doubles the page beyond the 800-word ideal. The reference content has only 4 code blocks, so the learner mostly reads instead of acting.
Evidence (quoted from the file):
Knowing which name maps to which role helps you follow workshop instructions without stopping to wonder what "the terminal" or "Codespaces" means in context.
Learning Science Rationale:
Sweller's Cognitive Load Theory predicts that long reference material introduced all at once overwhelms working memory and leaves little capacity for schema formation; the segmenting principle (Mayer) recommends splitting content into learner-paced chunks. Pairing each term with a quick verify command (retrieval practice) turns passive reading into active learning.
Improvement Prompt (for an agent):
Edit workshop/side-quest-01-02-environment-reference.md. Split the page so the main file stays under ~800 words: keep the glossary table and checkpoint, and move the "Conceptual screenshots" section (lines 83–195) into a new side-quest file (e.g. side-quest-01-04-environment-screenshots.md) linked from the main page. Add a short "Try it" code block after the glossary that runs `gh --version`, `git --version`, and `gh auth status`. Keep the existing `## :white_check_mark: Checkpoint` and `## :clipboard: Before You Start` headings, do not number headings, update workshop/README.md if a file is added, and run `npx --yes markdownlint-cli2 "**/*.md"`.
Expected Score After Fix: 6.5 / 10.0 (before scorer fix); 8.0+ after the scorer fix
Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · ~39 AIC · ⌖ ~1 AIC · ⊞ 5K · ◷
- expires on Nov 23, 2026, 4:03 AM UTC
- 主要语言
- JavaScript
- 星标
- 61
- 派生
- 43
- 平均合并
- 10 小时 38 分钟
- 30 天内合并 PR
- 12
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
githubnext/gh-aw-workshop 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
githubnext/gh-aw-workshop#6010 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 80/100
githubnext/gh-aw-workshop#6000 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 62/100
githubnext/gh-aw-workshop#5998 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 半天 新手友好度 70/100
githubnext/gh-aw-workshop#5996 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 78/100
githubnext/gh-aw-workshop#5997 ·
维护者通常 1 天内回复
查看 githubnext/gh-aw-workshop 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
ImranR98/apps.obtainium.imranr.dev#2023 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
Spomky-Labs/pwa-bundle#496 ·
维护者通常 5 天内回复