Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

upstream-echo

Estrelas21

Forks13

Atualizado9 de junho de 2026 às 06:18

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

the-oracle-keeps-the-human-human

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

Explorador de arquivos

13 arquivos

SKILL.md

readonly

name	upstream-echo
description	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.

/upstream-echo — Resonance Mapping

"ฟังก่อน แล้วสะท้อนกลับด้วยความหมาย" An echo is not just reflection — it is the same signal returning with new meaning.

Usage

/upstream-echo <owner/repo>                    # Last 14 days
/upstream-echo <owner/repo> --since 2026-05-25 # Custom window

Core Idea

Most digest tools count: how many commits? how many PRs? upstream-echo asks: what echoes?

An idea that appears in an issue, then a PR title, then multiple commits = resonance. A commit with no issue trail = noise, or an undisclosed decision. A long-open issue with no PR echo = blocked signal.

Steps

1. Gather All Signals (timestamp = SSOT)

REPO="$1"
SINCE="${2:-$(date -v-14d +%Y-%m-%d)}"

# Three sources, one timeline
gh api "repos/$REPO/commits?since=${SINCE}T00:00:00Z&per_page=100" --paginate
gh api "repos/$REPO/issues?since=${SINCE}T00:00:00Z&per_page=100&state=all" --paginate
gh api "repos/$REPO/pulls?state=all&per_page=100&sort=created&direction=desc" --paginate

2. Map Daily Activity (Pulse)

Group all events by day. Show commit + issue + PR on one bar — not three separate charts.

DATE        commits  prs  issues  ████ bar
──────────  ───────  ───  ──────  ─────────────────
2026-06-06  229      173  125     ██████████████████████████████  SPIKE
2026-06-07  104       75   63     ████████████████

3. Find Echo Patterns (Resonance Chains)

Extract keywords from titles. Track where they appear:

Issue opened with keyword → PR title has same keyword → commit message echoes it

ECHO: "wake"
  issue #2597  "maw wake doesn't restore context" (2026-06-08)
  PR #2606     "Let wake rehydrate only selected saved agents" (2026-06-09)
  commit       "Let wake rehydrate only selected saved agents" (2026-06-09)

This chain = intentional signal. Ideas that echo = things the team is thinking hard about.

4. Signal vs Noise Classification

SIGNAL   = echoes ≥2 sources (issue+PR, PR+commit, issue+commit)
NOISE    = bump/merge/ci commits with no issue trail
BLOCKED  = issue with no PR echo (idea stuck at proposal)
ORPHAN   = commit with no matching issue or PR (undisclosed decision)

5. Three-Line Verdict

PULSE:    repo is [active/cooling/spiking]
RESONANCE: top 3 echoing ideas
WATCH:    blocked/orphan signals that need attention

Rules

Run real commands — no mock data
Every claim backed by sha/issue#/PR#
Echo = same concept in ≥2 event types (not just same word twice in commits)
Show the chain, not just the count
Timestamp is the only authority

Mais deste repositório

mesmo repositório

atom-upstream-digest

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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

2026-06-3021

upstream-weight

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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.

2026-06-2121

upstream-hive

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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.

2026-06-0921

upstream-cortex

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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."

2026-06-0821

oracle-write-book

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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.

2026-06-0821

upstream-story

the-oracle-keeps-the-human-human/workshop-03-upstream-digest

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.

2026-06-0821

name	upstream-echo
description	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.

/upstream-echo — Resonance Mapping

"ฟังก่อน แล้วสะท้อนกลับด้วยความหมาย" An echo is not just reflection — it is the same signal returning with new meaning.

Usage

/upstream-echo <owner/repo>                    # Last 14 days
/upstream-echo <owner/repo> --since 2026-05-25 # Custom window

Core Idea

Most digest tools count: how many commits? how many PRs? upstream-echo asks: what echoes?

Steps

1. Gather All Signals (timestamp = SSOT)

REPO="$1"
SINCE="${2:-$(date -v-14d +%Y-%m-%d)}"

# Three sources, one timeline
gh api "repos/$REPO/commits?since=${SINCE}T00:00:00Z&per_page=100" --paginate
gh api "repos/$REPO/issues?since=${SINCE}T00:00:00Z&per_page=100&state=all" --paginate
gh api "repos/$REPO/pulls?state=all&per_page=100&sort=created&direction=desc" --paginate

2. Map Daily Activity (Pulse)

Group all events by day. Show commit + issue + PR on one bar — not three separate charts.

DATE        commits  prs  issues  ████ bar
──────────  ───────  ───  ──────  ─────────────────
2026-06-06  229      173  125     ██████████████████████████████  SPIKE
2026-06-07  104       75   63     ████████████████

3. Find Echo Patterns (Resonance Chains)

Extract keywords from titles. Track where they appear:

Issue opened with keyword → PR title has same keyword → commit message echoes it

ECHO: "wake"
  issue #2597  "maw wake doesn't restore context" (2026-06-08)
  PR #2606     "Let wake rehydrate only selected saved agents" (2026-06-09)
  commit       "Let wake rehydrate only selected saved agents" (2026-06-09)

This chain = intentional signal. Ideas that echo = things the team is thinking hard about.

4. Signal vs Noise Classification

SIGNAL   = echoes ≥2 sources (issue+PR, PR+commit, issue+commit)
NOISE    = bump/merge/ci commits with no issue trail
BLOCKED  = issue with no PR echo (idea stuck at proposal)
ORPHAN   = commit with no matching issue or PR (undisclosed decision)

5. Three-Line Verdict

PULSE:    repo is [active/cooling/spiking]
RESONANCE: top 3 echoing ideas
WATCH:    blocked/orphan signals that need attention

Rules

Run real commands — no mock data
Every claim backed by sha/issue#/PR#
Echo = same concept in ≥2 event types (not just same word twice in commits)
Show the chain, not just the count
Timestamp is the only authority