gstack openclaw retro

Engineering Community

Skill notes

Arguments

Default: last 7 days 24h: last 24 hours 14d: last 14 days 30d: last 30 days compare: compare current window vs prior same-length window

Instructions

Parse the argument to determine the time window. Default to 7 days. All times should be reported in the user's local timezone. Midnight-aligned windows: For day units, compute an absolute start date at local midnight. 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. For hour units, use --since="N hours ago".

Step 1: Gather Raw Data

First, fetch origin and identify the current user: The name returned by git config user.name is "you" ... the person reading this retro. All other authors are teammates. Run ALL of these git commands (they are independent):

Step 2: Compute Metrics

Calculate and present these metrics in a summary: Commits to main: N Contributors: N PRs merged: N Total insertions: N

Step 3: Commit Time Distribution

Show hourly histogram in local time: Identify: Peak hours Dead zones Bimodal pattern (morning/evening) vs continuous

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather Raw Data

First, fetch origin and identify the current user: The name returned by `git config user.name` is "you" ... the person reading this retro. All other authors are teammates. Run ALL of these git commands (they are independent):

02
Step 2: Compute Metrics

Calculate and present these metrics in a summary: Commits to main: N Contributors: N PRs merged: N Total insertions: N

03
Step 3: Commit Time Distribution

Show hourly histogram in local time: Identify: Peak hours Dead zones Bimodal pattern (morning/evening) vs continuous

04
Step 4: Work Session Detection

Detect sessions using 45-minute gap threshold between consecutive commits. Classify sessions: Deep sessions (50+ min) Medium sessions (20-50 min) Micro sessions (<20 min, single-commit)

05
Step 5: Commit Type Breakdown

Categorize by conventional commit prefix (feat/fix/refactor/test/chore/docs). Show as percentage bar: Flag if fix ratio exceeds 50% ... signals a "ship fast, fix fast" pattern that may indicate review gaps.

06
Step 6: Hotspot Analysis

Show top 10 most-changed files. Flag: Files changed 5+ times (churn hotspots) Test files vs production files in the hotspot list VERSION/CHANGELOG frequency

07
Step 7: PR Size Distribution

Estimate PR sizes and bucket them: Small (<100 LOC) Medium (100-500 LOC) Large (500-1500 LOC) XL (1500+ LOC)

08
Step 8: Focus Score + Ship of the Week

Focus score: Percentage of commits touching the single most-changed top-level directory. Higher = deeper focused work. Lower = scattered context-switching. Ship of the week: The single highest-LOC PR in the window. Highlight PR number, LOC changed, and why it matters.

09
Step 9: Team Member Analysis

For each contributor (including the current user), compute: Commits and LOC ... total commits, insertions, deletions, net LOC Areas of focus ... which directories/files they touched most (top 3) Commit type mix ... their personal feat/fix/refactor/test breakdown Session patterns ... when they code (peak hours), session count

10
Step 10: Week-over-Week Trends (if window >= 14d)

Split into weekly buckets and show trends: Commits per week (total and per-author) LOC per week Test ratio per week Fix ratio per week

11
Step 11: Streak Tracking

Count consecutive days with at least 1 commit, going back from today: Display both: "Team shipping streak: 47 consecutive days" "Your shipping streak: 32 consecutive days"

12
Step 12: Load History & Compare

Check for prior retro history in `memory/`: If prior retros exist, load the most recent one and calculate deltas: If no prior retros exist, note "First retro recorded, run again next week to see trends."

13
Step 13: Save Retro History

Save a JSON snapshot to `memory/retro-YYYY-MM-DD.json` with metrics, authors, version range, streak, and tweetable summary.

14
Step 14: Write the Narrative

Format for Telegram (bullets, bold, no markdown tables in the final output). Structure: Tweetable summary (first line): Week of Mar 1: 47 commits (3 contributors), 3.2k LOC, 38% tests, 12 PRs, peak: 10pm | Streak: 47d Then sections:

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.