workshop-03-upstream-digest

Digest a GitHub repository into a timestamp-first human-readable activity timeline.

Digest a repo's recent activity by WEIGHT, not by commit count — lines changed, churn (added-then-deleted = motion not progress), and where the real heft landed per day & area. Classifies by verb→intent so imperative titles (Keep/Cover/Prevent) don't fall into "other". Use when user says "upstream weight", "what really shipped", "digest <repo> by heft", or wants to know which day was real surgery vs just busy.

Digest a repo by tracing connections — which files move together, which PRs close which issues, who works at what hour. A bee's-eye view of the hive. Merges commits+PRs+issues on one timestamp axis, detects co-change clusters (files that always ship together = hidden coupling), maps contributor rhythm (timezone/hour heatmap), and highlights cause→effect chains (issue opened → PR merged → issue closed). Reruns on any repo. Use to understand "how does this team actually work?" in 30 seconds.

Resonance mapping — traces how ideas echo through a repo's timeline. Shows when a concept first appears in issues, returns in PRs, and lands in commits. Timestamp = SSOT. Finds signal by mapping pattern recurrence, not just frequency.

Digest a repo's recent activity the way a cortex consolidates memory — not a flat commit count, but 3 cortical layers (L1 Surface = what changed per day, L2 Association = braid commits+PRs+issues on one timestamp axis to expose issue→close latency, L3 Consolidation = rank days by MEMORY WEIGHT where feat/fix that lands weighs heavy, bump/chore decays, reverts are negative "forgetting"). Surfaces the "quality day" (high weight-per-commit) that a raw count hides, plots a forgetting curve (signal vs noise vs revert), and lists retained-memory highlights. Reruns on any repo via digest.sh (portable awk, macOS+Linux). Use to understand "what upstream actually RETAINED lately" in 30 seconds — not just "how many commits."

Write a structured long-form book or booklet (multi-chapter document, 10+ pages) from a topic or set of notes, then render it to a polished PDF. Handles outline → chapter drafting → prose polish → code/diagrams → PDF render → delivery. TRIGGER when: user asks to 'write a book', 'เขียนหนังสือ', 'ทำหนังสือ', 'write-book', make a booklet/ebook/guide of N pages, turn notes/a workshop/a topic into a long-form document, or compile learnings into a readable book. DO NOT TRIGGER for: a single blog post or article (use kien-thai), a README, short docs, slides, or a one-page summary.

Digest a repo's recent commits into a STORY (not a count), then braid commits+PRs+issues on one timestamp axis so cause→effect is visible. Reads N days of history, groups by day, traces the one big narrative arc, and separates new-signal from version-noise from churn (test added-then-deleted, reverts). Handles non-conventional commit messages. Reruns on any repo via digest.sh. Use to understand "what landed upstream lately" + "how did it unfold?" in 30 seconds.

Write a technical / course-style book that teaches readers to BUILD something themselves — architecture → step-by-step → real code → exercises → troubleshooting → render PDF + images → publish. Use when user says 'technical book', 'เล่มสอง', 'course book', 'เขียนคู่มือเทคนิค', or wants a how-to/reproducible guide (vs the overview/story style of /oracle-write-book).

5-lens upstream analysis — commits + issues + PRs merged by timestamp. See what a flat log hides.

เขียนหนังสือจากประสบการณ์ที่เรียนรู้ — แปลง token ที่ใช้ไปเป็นหนังสือสอนคนอื่น ใช้ /kien-thai เป็น engine เขียนภาษาไทยที่อ่านง่าย

Health check ของ upstream repo — unified timeline (commits + issues + PRs) วิเคราะห์ tempo, area heatmap, signal/noise, correlation, และ impact ให้เข้าใจใน 30 วิ

สรุปว่า repo หนึ่ง "มี commit อะไรเข้ามาบ้าง" ให้คนอ่านเข้าใจใน 30 วิ (Timeline + Classification + Highlights + Area Analysis)

Digest a repo's recent activity (commits + PRs + issues) into a plain-language courier brief. Story arc, not stats — written for non-developers.

Use to digest a repo's recent commits through multiple prism lenses — not just "what type" (feat/fix) but "what area" and "signal vs noise" — so a human understands what actually changed in 30 seconds. Fuses /oracle-prism multi-lens analysis into upstream digest.

Write Thai-language prose (technical documentation, marketing copy, explainers, blog posts, translations) that reads like a real Thai writer — not generic AI output. Counters training-data skew toward over-formal, over-polite, calqued Thai. TRIGGER when: user asks for any non-trivial Thai prose output (paragraph or longer — blog post, landing page, doc page, README in Thai, email, announcement, section); user asks to translate English into Thai; user asks to edit, rewrite, or review existing Thai prose; conversation is in Thai and user asks for a prose deliverable. DO NOT TRIGGER for: single-word or single-phrase translations, button labels, code identifiers, short UI strings, code comments, or conversational chat replies in Thai that aren't deliverable prose.

Write + render + publish a guide/book from a topic — topic → Markdown → PDF → images → Discord, in one flow. Use when user says 'write book', 'เขียนหนังสือ', 'เขียน guide', 'ทำเป็น PDF', 'oracle-write-book', or wants a session/topic turned into a publishable illustrated guide.

Measure the RHYTHM of a repo's full activity stream — commits + issues + PRs unified on TIMESTAMP as single source of truth. Reveals cause-effect chains (issue → PR → commit → bump), hourly distribution, author voices, spike detection, signal-vs-noise, dharma lifecycle. Use when user says 'pulse', 'rhythm', 'repo heartbeat', 'upstream pulse', 'unified timeline', wants to feel the energy of a repo not just digest commits, or wants to see issue→PR→commit causal flow. Companion to ChaiKlang's /upstream-digest (which focuses on commit classification). Pulse focuses on cross-source rhythm + life signs.