القائمة
5-lens upstream analysis — commits + issues + PRs merged by timestamp. See what a flat log hides.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | upstream-lens |
| description | 5-lens upstream analysis — commits + issues + PRs merged by timestamp. See what a flat log hides. |
"A flat log shows WHAT happened. Five lenses show WHAT IT MEANS."
/upstream-lens <owner/repo> # Last 14 days
/upstream-lens <owner/repo> --since 2026-05-25 # Custom range
REPO="$1"
SINCE="$2" # default: 14 days ago
# Commits
gh api "repos/$REPO/commits?since=${SINCE}T00:00:00Z&per_page=100" --paginate
# Issues
gh api "repos/$REPO/issues?since=${SINCE}T00:00:00Z&per_page=100&state=all" --paginate
# PRs
gh api "repos/$REPO/pulls?state=all&per_page=100&sort=created&direction=desc" --paginate
Merge all by timestamp (SSOT). Tag each: [commit] [issue] [pr].
VERDICT: [one line — state of the repo]
SIGNAL: [what to watch]
NOISE: [what to ignore]