Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[curriculum-eval] 04-github-actions-intro.md: cognitive_load — labeling exercise deferred to end instead of interleaved after each concept chunk

クローズ 初心者向け
  • 何か問題がありますか？
#4,400 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
65/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, markdown
領域
content, documentation

調査の方向性

workshop/04-github-actions-intro.md から始めます：「Quick Refresher」セクションの hello-workflow.yml の例、「Why This Matters for Agentic Workflows」テーブル、末尾付近の「Label a sample workflow」演習です。その演習をリフレッシャーの直後に移動し、比較テーブルの後に想起質問を1つ追加し、Checkpoint セクションがまだ一致することを確認してください。ページがその順序で読まれ、npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md" が成功したら完了です。

索引モデルが issue の本文から書いたものです。

説明

curriculum documentation quality

File: workshop/04-github-actions-intro.md
Overall Score: 5.39 / 10.0 (corpus mean: 6.09)

Flagged Dimensions:

Dimension Score Benchmark Delta
cognitive_load 6.8 ≤15 new concepts → 10 −3.2
active_learning 3.9 density ≥ 3.0 → 10 −0 (borderline; flagged alongside concept overload)

Root Cause (≤ 2 sentences):
The page defines 28 new concepts in 756 words (≈3.7 concepts per 100 words), introducing the entire Actions vocabulary (trigger, job, runner, step, action, on, runs-on, self-hosted runner, YAML structure) plus a parallel agentic-workflow comparison table in one pass, which is unusually dense for a page explicitly framed as a "5 Minutes" refresher for likely-familiar material. The skip-ahead <details> at the top signals this is meant to be fast for experienced learners, but the full page still front-loads nearly twice the ideal concept count for anyone who doesn't skip.

Evidence (quoted from the file):

when to run (on) ... what to run (jobs) ... how each job executes (steps)

| Concept | Classic Actions | Agentic Workflow | ... (five-row comparison table introduced immediately after the five Actions primitives, before any practice)

Learning Science Rationale:
Bloom's Taxonomy places this page at "Understand" (confirmed by the tool's own bloom_reclassification), which is appropriate for a refresher, but Cognitive Load Theory still applies: presenting five new primitives (trigger/job/runner/step/action) immediately followed by a second five-row comparison table before any hands-on labeling task creates two dense conceptual layers with only one practice checkpoint ("Label a sample workflow") positioned after both, rather than one practice moment per layer — germane load is better managed when practice is interleaved per chunk rather than deferred to the end of accumulated new material.

Improvement Prompt (for an agent):

Open workshop/04-github-actions-intro.md and interleave practice earlier:

1. Move the existing "Label a sample workflow" labeling exercise (currently near the end, after the "Why This Matters for Agentic Workflows" comparison table) to appear directly after the "Quick Refresher" section and its annotated hello-workflow.yml example — i.e., right after the five Actions primitives are introduced, before the agentic-workflow comparison table.
2. Keep the "Why This Matters for Agentic Workflows" comparison table but add one short retrieval question immediately after it (e.g., "Which row changes between classic and agentic — the trigger, the runner, or the output path?") in a <details> reveal, so the comparison table gets its own practice moment instead of deferring to the final "Try it" activity.
3. Consider trimming the "What is a runner?" collapsible aside to a single sentence plus the existing code snippet, since self-hosted runners are a side detail relative to the core five primitives this page is teaching.
4. Verify the "## :white_check_mark: Checkpoint" section still matches the reordered content.
5. Run `npx --yes markdownlint-cli2 "workshop/04-github-actions-intro.md"` and fix any lint errors.

Expected Score After Fix: 6.2–6.6 / 10.0

Generated by 🔬 Curriculum Quality Evaluator · copilot · auto · 117 AIC · ⌖ 19.4 AIC · ⊞ 10.4K · ◷

  • expires on Oct 11, 2026, 2:04 AM UTC
主要言語
JavaScript
スター
55
フォーク
36
平均マージ
2日 6時間
マージ済み PR（30日）
18

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートなし
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

githubnext/gh-aw-workshop のほかの issue

githubnext/gh-aw-workshop の issue をすべて見る

似ている issue

JavaScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。