garrytan · garrytan · Mar 22, 2026 · Mar 22, 2026 · Mar 22, 2026 · Mar 22, 2026
diff --git a/.agents/skills/gstack-retro/SKILL.md b/.agents/skills/gstack-retro/SKILL.md
@@ -273,24 +273,30 @@ When the user types `/retro`, run this skill.
 - `/retro 30d` — last 30 days
 - `/retro compare` — compare current window vs prior same-length window
 - `/retro compare 14d` — compare with explicit window
+- `/retro global` — cross-project retro across all AI coding tools (7d default)
+- `/retro global 14d` — cross-project retro with explicit window
 
 ## Instructions
 
 Parse the argument to determine the time window. Default to 7 days if no argument given. All times should be reported in the user's **local timezone** (use the system default — do NOT set `TZ`).
 
 **Midnight-aligned windows:** For day (`d`) and week (`w`) units, compute an absolute start date at local midnight, not a relative string. For example, if today is 2026-03-18 and the window is 7 days: the start date is 2026-03-11. Use `--since="2026-03-11T00:00:00"` for git log queries — the explicit `T00:00:00` suffix ensures git starts from midnight. Without it, git uses the current wall-clock time (e.g., `--since="2026-03-11"` at 11pm means 11pm, not midnight). For week units, multiply by 7 to get days (e.g., `2w` = 14 days back). For hour (`h`) units, use `--since="N hours ago"` since midnight alignment does not apply to sub-day windows.
 
-**Argument validation:** If the argument doesn't match a number followed by `d`, `h`, or `w`, the word `compare`, or `compare` followed by a number and `d`/`h`/`w`, show this usage and stop:
+**Argument validation:** If the argument doesn't match a number followed by `d`, `h`, or `w`, the word `compare` (optionally followed by a window), or the word `global` (optionally followed by a window), show this usage and stop:
 ```
-Usage: /retro [window]
+Usage: /retro [window | compare | global]
   /retro              — last 7 days (default)
   /retro 24h          — last 24 hours
   /retro 14d          — last 14 days
   /retro 30d          — last 30 days
   /retro compare      — compare this period vs prior period
   /retro compare 14d  — compare with explicit window
+  /retro global       — cross-project retro across all AI tools (7d default)
+  /retro global 14d   — cross-project retro with explicit window
 ```
 
+**If the first argument is `global`:** Skip the normal repo-scoped retro (Steps 1-14). Instead, follow the **Global Retrospective** flow at the end of this document. The optional second argument is the time window (default 7d). This mode does NOT require being inside a git repo.
+
 ### Step 1: Gather Raw Data
 
 First, fetch origin and identify the current user:
@@ -736,6 +742,293 @@ Small, practical, realistic. Each must be something that takes <5 minutes to ado
 
 ---
 
+## Global Retrospective Mode
+
+When the user runs `/retro global` (or `/retro global 14d`), follow this flow instead of the repo-scoped Steps 1-14. This mode works from any directory — it does NOT require being inside a git repo.
+
+### Global Step 1: Compute time window
+
+Same midnight-aligned logic as the regular retro. Default 7d. The second argument after `global` is the window (e.g., `14d`, `30d`, `24h`).
+
+### Global Step 2: Run discovery
+
+Locate and run the discovery script using this fallback chain:
+
+```bash
+DISCOVER_BIN=""
+[ -x ~/.codex/skills/gstack/bin/gstack-global-discover ] && DISCOVER_BIN=~/.codex/skills/gstack/bin/gstack-global-discover
+[ -z "$DISCOVER_BIN" ] && [ -x .agents/skills/gstack/bin/gstack-global-discover ] && DISCOVER_BIN=.agents/skills/gstack/bin/gstack-global-discover
+[ -z "$DISCOVER_BIN" ] && which gstack-global-discover >/dev/null 2>&1 && DISCOVER_BIN=$(which gstack-global-discover)
+[ -z "$DISCOVER_BIN" ] && [ -f bin/gstack-global-discover.ts ] && DISCOVER_BIN="bun run bin/gstack-global-discover.ts"
+echo "DISCOVER_BIN: $DISCOVER_BIN"
+```
+
+If no binary is found, tell the user: "Discovery script not found. Run `bun run build` in the gstack directory to compile it." and stop.
+
+Run the discovery:
+```bash
+$DISCOVER_BIN --since "<window>" --format json 2>/tmp/gstack-discover-stderr
+```
+
+Read the stderr output from `/tmp/gstack-discover-stderr` for diagnostic info. Parse the JSON output from stdout.
+
+If `total_sessions` is 0, say: "No AI coding sessions found in the last <window>. Try a longer window: `/retro global 30d`" and stop.
+
+### Global Step 3: Run git log on each discovered repo
+
+For each repo in the discovery JSON's `repos` array, find the first valid path in `paths[]` (directory exists with `.git/`). If no valid path exists, skip the repo and note it.
+
+**For local-only repos** (where `remote` starts with `local:`): skip `git fetch` and use the local default branch. Use `git log HEAD` instead of `git log origin/$DEFAULT`.
+
+**For repos with remotes:**
+
+```bash
+git -C <path> fetch origin --quiet 2>/dev/null
+```
+
+Detect the default branch for each repo: first try `git symbolic-ref refs/remotes/origin/HEAD`, then check common branch names (`main`, `master`), then fall back to `git rev-parse --abbrev-ref HEAD`. Use the detected branch as `<default>` in the commands below.
+
+```bash
+# Commits with stats
+git -C <path> log origin/$DEFAULT --since="<start_date>T00:00:00" --format="%H|%aN|%ai|%s" --shortstat
+
+# Commit timestamps for session detection, streak, and context switching
+git -C <path> log origin/$DEFAULT --since="<start_date>T00:00:00" --format="%at|%aN|%ai|%s" | sort -n
+
+# Per-author commit counts
+git -C <path> shortlog origin/$DEFAULT --since="<start_date>T00:00:00" -sn --no-merges
+
+# PR numbers from commit messages
+git -C <path> log origin/$DEFAULT --since="<start_date>T00:00:00" --format="%s" | grep -oE '#[0-9]+' | sort -n | uniq
+```
+
+For repos that fail (deleted paths, network errors): skip and note "N repos could not be reached."
+
+### Global Step 4: Compute global shipping streak
+
+For each repo, get commit dates (capped at 365 days):
+
+```bash
+git -C <path> log origin/$DEFAULT --since="365 days ago" --format="%ad" --date=format:"%Y-%m-%d" | sort -u
+```
+
+Union all dates across all repos. Count backward from today — how many consecutive days have at least one commit to ANY repo? If the streak hits 365 days, display as "365+ days".
+
+### Global Step 5: Compute context switching metric
+
+From the commit timestamps gathered in Step 3, group by date. For each date, count how many distinct repos had commits that day. Report:
+- Average repos/day
+- Maximum repos/day
+- Which days were focused (1 repo) vs. fragmented (3+ repos)
+
+### Global Step 6: Per-tool productivity patterns
+
+From the discovery JSON, analyze tool usage patterns:
+- Which AI tool is used for which repos (exclusive vs. shared)
+- Session count per tool
+- Behavioral patterns (e.g., "Codex used exclusively for myapp, Claude Code for everything else")
+
+### Global Step 7: Aggregate and generate narrative
+
+Structure the output with the **shareable personal card first**, then the full
+team/project breakdown below. The personal card is designed to be screenshot-friendly
+— everything someone would want to share on X/Twitter in one clean block.
+
+---
+
+**Tweetable summary** (first line, before everything else):
+```
+Week of Mar 14: 5 projects, 138 commits, 250k LOC across 5 repos | 48 AI sessions | Streak: 52d 🔥
+```
+
+## 🚀 Your Week: [user name] — [date range]
+
+This section is the **shareable personal card**. It contains ONLY the current user's
+stats — no team data, no project breakdowns. Designed to screenshot and post.
+
+Use the user identity from `git config user.name` to filter all per-repo git data.
+Aggregate across all repos to compute personal totals.
+
+Render as a single visually clean block. Left border only — no right border (LLMs
+can't align right borders reliably). Pad repo names to the longest name so columns
+align cleanly. Never truncate project names.
+
+```
+╔═══════════════════════════════════════════════════════════════
+║  [USER NAME] — Week of [date]
+╠═══════════════════════════════════════════════════════════════
+║
+║  [N] commits across [M] projects
+║  +[X]k LOC added · [Y]k LOC deleted · [Z]k net
+║  [N] AI coding sessions (CC: X, Codex: Y, Gemini: Z)
+║  [N]-day shipping streak 🔥
+║
+║  PROJECTS
+║  ─────────────────────────────────────────────────────────
+║  [repo_name_full]        [N] commits    +[X]k LOC    [solo/team]
+║  [repo_name_full]        [N] commits    +[X]k LOC    [solo/team]
+║  [repo_name_full]        [N] commits    +[X]k LOC    [solo/team]
+║
+║  SHIP OF THE WEEK
+║  [PR title] — [LOC] lines across [N] files
+║
+║  TOP WORK
+║  • [1-line description of biggest theme]
+║  • [1-line description of second theme]
+║  • [1-line description of third theme]
+║
+║  Powered by gstack · github.com/garrytan/gstack
+╚═══════════════════════════════════════════════════════════════
+```
+
+**Rules for the personal card:**
+- Only show repos where the user has commits. Skip repos with 0 commits.
+- Sort repos by user's commit count descending.
+- **Never truncate repo names.** Use the full repo name (e.g., `analyze_transcripts`
+  not `analyze_trans`). Pad the name column to the longest repo name so all columns
+  align. If names are long, widen the box — the box width adapts to content.
+- For LOC, use "k" formatting for thousands (e.g., "+64.0k" not "+64010").
+- Role: "solo" if user is the only contributor, "team" if others contributed.
+- Ship of the Week: the user's single highest-LOC PR across ALL repos.
+- Top Work: 3 bullet points summarizing the user's major themes, inferred from
+  commit messages. Not individual commits — synthesize into themes.
+  E.g., "Built /retro global — cross-project retrospective with AI session discovery"
+  not "feat: gstack-global-discover" + "feat: /retro global template".
+- The card must be self-contained. Someone seeing ONLY this block should understand
+  the user's week without any surrounding context.
+- Do NOT include team members, project totals, or context switching data here.
+
+**Personal streak:** Use the user's own commits across all repos (filtered by
+`--author`) to compute a personal streak, separate from the team streak.
+
+---
+
+## Global Engineering Retro: [date range]
+
+Everything below is the full analysis — team data, project breakdowns, patterns.
+This is the "deep dive" that follows the shareable card.
+
+### All Projects Overview
+| Metric | Value |
+|--------|-------|
+| Projects active | N |
+| Total commits (all repos, all contributors) | N |
+| Total LOC | +N / -N |
+| AI coding sessions | N (CC: X, Codex: Y, Gemini: Z) |
+| Active days | N |
+| Global shipping streak (any contributor, any repo) | N consecutive days |
+| Context switches/day | N avg (max: M) |
+
+### Per-Project Breakdown
+For each repo (sorted by commits descending):
+- Repo name (with % of total commits)
+- Commits, LOC, PRs merged, top contributor
+- Key work (inferred from commit messages)
+- AI sessions by tool
+
+**Your Contributions** (sub-section within each project):
+For each project, add a "Your contributions" block showing the current user's
+personal stats within that repo. Use the user identity from `git config user.name`
+to filter. Include:
+- Your commits / total commits (with %)
+- Your LOC (+insertions / -deletions)
+- Your key work (inferred from YOUR commit messages only)
+- Your commit type mix (feat/fix/refactor/chore/docs breakdown)
+- Your biggest ship in this repo (highest-LOC commit or PR)
+
+If the user is the only contributor, say "Solo project — all commits are yours."
+If the user has 0 commits in a repo (team project they didn't touch this period),
+say "No commits this period — [N] AI sessions only." and skip the breakdown.
+
+Format:
+```
+**Your contributions:** 47/244 commits (19%), +4.2k/-0.3k LOC
+  Key work: Writer Chat, email blocking, security hardening
+  Biggest ship: PR #605 — Writer Chat eats the admin bar (2,457 ins, 46 files)
+  Mix: feat(3) fix(2) chore(1)
+```
+
+### Cross-Project Patterns
+- Time allocation across projects (% breakdown, use YOUR commits not total)
+- Peak productivity hours aggregated across all repos
+- Focused vs. fragmented days
+- Context switching trends
+
+### Tool Usage Analysis
+Per-tool breakdown with behavioral patterns:
+- Claude Code: N sessions across M repos — patterns observed
+- Codex: N sessions across M repos — patterns observed
+- Gemini: N sessions across M repos — patterns observed
+
+### Ship of the Week (Global)
+Highest-impact PR across ALL projects. Identify by LOC and commit messages.
+
+### 3 Cross-Project Insights
+What the global view reveals that no single-repo retro could show.
+
+### 3 Habits for Next Week
+Considering the full cross-project picture.
+
+---
+
+### Global Step 8: Load history & compare
+
+```bash
+ls -t ~/.gstack/retros/global-*.json 2>/dev/null | head -5
+```
+
+**Only compare against a prior retro with the same `window` value** (e.g., 7d vs 7d). If the most recent prior retro has a different window, skip comparison and note: "Prior global retro used a different window — skipping comparison."
+
+If a matching prior retro exists, load it with the Read tool. Show a **Trends vs Last Global Retro** table with deltas for key metrics: total commits, LOC, sessions, streak, context switches/day.
+
+If no prior global retros exist, append: "First global retro recorded — run again next week to see trends."
+
+### Global Step 9: Save snapshot
+
+```bash
+mkdir -p ~/.gstack/retros
+```
+
+Determine the next sequence number for today:
+```bash
+today=$(date +%Y-%m-%d)
+existing=$(ls ~/.gstack/retros/global-${today}-*.json 2>/dev/null | wc -l | tr -d ' ')
+next=$((existing + 1))
+```
+
+Use the Write tool to save JSON to `~/.gstack/retros/global-${today}-${next}.json`:
+
+```json
+{
+  "type": "global",
+  "date": "2026-03-21",
+  "window": "7d",
+  "projects": [
+    {
+      "name": "gstack",
+      "remote": "https://github.com/garrytan/gstack",
+      "commits": 47,
+      "insertions": 3200,
+      "deletions": 800,
+      "sessions": { "claude_code": 15, "codex": 3, "gemini": 0 }
+    }
+  ],
+  "totals": {
+    "commits": 182,
+    "insertions": 15300,
+    "deletions": 4200,
+    "projects": 5,
+    "active_days": 6,
+    "sessions": { "claude_code": 48, "codex": 8, "gemini": 3 },
+    "global_streak_days": 52,
+    "avg_context_switches_per_day": 2.1
+  },
+  "tweetable": "Week of Mar 14: 5 projects, 182 commits, 15.3k LOC | CC: 48, Codex: 8, Gemini: 3 | Focus: gstack (58%) | Streak: 52d"
+}
+```
+
+---
+
 ## Compare Mode
 
 When the user runs `/retro compare` (or `/retro compare 14d`):
@@ -769,3 +1062,4 @@ When the user runs `/retro compare` (or `/retro compare 14d`):
 - Treat merge commits as PR boundaries
 - Do not read CLAUDE.md or other docs — this skill is self-contained
 - On first run (no prior retros), skip comparison sections gracefully
+- **Global mode:** Does NOT require being inside a git repo. Saves snapshots to `~/.gstack/retros/` (not `.context/retros/`). Gracefully skip AI tools that aren't installed. Only compare against prior global retros with the same window value. If streak hits 365d cap, display as "365+ days".
diff --git a/.gitignore b/.gitignore
@@ -1,6 +1,7 @@
 .env
 node_modules/
 browse/dist/
+bin/gstack-global-discover
 .gstack/
 .claude/skills/
 .context/

diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.11.1.0] - 2026-03-22 — Global Retro: Cross-Project AI Coding Retrospective
+
+### Added
+
+- **`/retro global` — see everything you shipped across every project in one report.** Scans your Claude Code, Codex CLI, and Gemini CLI sessions, traces each back to its git repo, deduplicates by remote, then runs a full retro across all of them. Global shipping streak, context-switching metrics, per-project breakdowns with personal contributions, and cross-tool usage patterns. Run `/retro global 14d` for a two-week view.
+- **Per-project personal contributions in global retro.** Each project in the global retro now shows YOUR commits, LOC, key work, commit type mix, and biggest ship — separate from team totals. Solo projects say "Solo project — all commits are yours." Team projects you didn't touch show session count only.
+- **`gstack-global-discover` — the engine behind global retro.** Standalone discovery script that finds all AI coding sessions on your machine, resolves working directories to git repos, normalizes SSH/HTTPS remotes for dedup, and outputs structured JSON. Compiled binary ships with gstack — no `bun` runtime needed.
+
+### Fixed
+
+- **Discovery script reads only the first few KB of session files** instead of loading entire multi-MB JSONL transcripts into memory. Prevents OOM on machines with extensive coding history.
+- **Claude Code session counts are now accurate.** Previously counted all JSONL files in a project directory; now only counts files modified within the time window.
+- **Week windows (`1w`, `2w`) are now midnight-aligned** like day windows, so `/retro global 1w` and `/retro global 7d` produce consistent results.
+
 ## [0.11.0.0] - 2026-03-22 — /cso: Zero-Noise Security Audits
 
 ### Added
@@ -54,12 +68,6 @@
 
 - **`/autoplan` — one command, fully reviewed plan.** Hand it a rough plan and it runs the full CEO → design → eng review pipeline automatically. Reads the actual review skill files from disk (same depth, same rigor as running each review manually) and makes intermediate decisions using 6 encoded principles: completeness, boil lakes, pragmatic, DRY, explicit over clever, bias toward action. Taste decisions (close approaches, borderline scope, codex disagreements) surface at a final approval gate. You approve, override, interrogate, or revise. Saves a restore point so you can re-run from scratch. Writes review logs compatible with `/ship`'s dashboard.
 
-## [0.9.9.0] - 2026-03-21 — Harder Office Hours
-
-### Changed
-
-- **`/office-hours` now pushes back harder.** The diagnostic questions no longer soften toward confident founders. Five changes: hardened response posture ("direct to the point of discomfort"), anti-sycophancy rules (banned phrases like "that's an interesting approach"), 5 worked pushback patterns showing BAD vs GOOD responses, a post-Q1 framing check that challenges undefined terms and hidden assumptions, and a gated escape hatch that asks 2 more questions before letting founders skip. Inspired by user feedback comparing gstack with dontbesilent's diagnostic skill.
-
 ## [0.9.8.0] - 2026-03-21 — Deploy Pipeline + E2E Performance
 
 ### Added

diff --git a/CLAUDE.md b/CLAUDE.md
@@ -78,7 +78,8 @@ gstack/
 ├── land-and-deploy/ # /land-and-deploy skill (merge → deploy → canary verify)
 ├── office-hours/    # /office-hours skill (YC Office Hours — startup diagnostic + builder brainstorm)
 ├── investigate/     # /investigate skill (systematic root-cause debugging)
-├── retro/           # Retrospective skill
+├── retro/           # Retrospective skill (includes /retro global cross-project mode)
+├── bin/             # Standalone scripts (gstack-global-discover for cross-tool session discovery)
 ├── document-release/ # /document-release skill (post-ship doc updates)
 ├── cso/             # /cso skill (OWASP Top 10 + STRIDE security audit)
 ├── design-consultation/ # /design-consultation skill (design system from scratch)