retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint.
npx skills add majiayu000/claude-skill-registry --skill gstack-retro --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Generates a weekly or time-windowed retrospective by analyzing commit history, work patterns, and code quality metrics. It identifies the user running the command and then analyzes every contributor with per-person praise and growth opportunities. Designed for senior IC/CTO-level builders using Claude Code.
How it works
- Parses the invocation to determine the time window, with defaults and variants described in the Arguments section. Windows include last 7 days by default, last 24 hours, last 14 days, last 30 days, or compare modes.
- Aligns windows to local time, using midnight boundaries for day and week units, and uses explicit --since timestamps for git log queries. For hours, uses an hours-ago formulation.
- Validates the argument to ensure it matches allowed patterns; otherwise, it prints usage text and stops.
- Step 1: Gather Raw Data: runs a git fetch origin <default> --quiet and determines the current user via git config user.name and git config user.email.
- Further steps (not shown in the excerpt) would likely aggregate metrics and produce a structured retrospective with per-contributor analysis and growth opportunities.
When to use it
Use when you want a team-wide, time-bounded retrospective that highlights individual contributions, patterns, and code-quality trends; invoked via /retro or /retro <window>.
What it can touch
- Tools: claude-code (declared)
- Commands: git fetch origin <default> --quiet, git config user.name, git config user.email
- Time handling in git log queries with --since flags (formatted per rules in the instruction)
Caveats
- The excerpt specifies a strict window alignment and argument validation; ensure local timezone handling is correct and that the origin default branch is determined externally by the default branch logic.
- The current content only covers initial data gathering; complete behavior depends on subsequent steps not shown here.
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs --> ## Preamble (run first) ```bash _UPD=$(~/.codex/skills/gstack/bin/gstack-update-check 2>/dev/null || .agents/skills/gstack/bin/gstack-update-check 2>/dev/null || true) [ -n "$_UPD" ] && echo "$_UPD" || true mkdir -p ~/.gstack/sessions touch ~/.gstack/sessions/"$PPID" _SESSIONS=$(find ~/.gstack/sessions -mmin -120 -type f 2>/dev/null | wc -l | tr -d ' ') find ~/.gstack/sessions -mmin +120 -type f -delete 2>/dev/null || true _CONTRIB=$(~/.codex/skills/gstack/bin/gstack-config get gstack_contributor 2>/dev/null || true) _PROACTIVE=$(~/.codex/skills/gstack/bin/gstack-config get proactive 2>/dev/null || echo "true") _BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown") echo "BRANCH: $_BRANCH" echo "PROACTIVE: $_PROACTIVE" _LAKE_SEEN=$([ -f ~/.gstack/.completeness-intro-seen ] && echo "yes" || echo "no") echo "LAKE_INTRO: $_LAKE_SEEN" _TEL=$(~/.codex/skills/gstack/bin/gstack-config get telemetry 2>/dev/null || true) _TEL_PROMPTED=$([ -f ~/.gstack/.telemetry-prompted ] && echo "yes" || echo "no") _TEL_START=$(date +%s) _SESSION_ID="$$-$(date +%s)" echo "TELEMETRY: ${_
- Preamble (run first)
- AskUserQuestion Format
- Completeness Principle — Boil the Lake
- Search Before Building
- Contributor Mode
- Completion Status Protocol
- Escalation
- Telemetry (run last)
- Detect default branch
- User-invocable
- Arguments
- Instructions
- Step 1: Gather Raw Data
- Step 2: Compute Metrics
mkdir -p ~/.gstack/sessions
touch ~/.gstack/sessions/"$PPID"
find ~/.gstack/sessions -mmin +120 -type f -delete 2>/dev/null || true
echo "BRANCH: $_BRANCH"
echo "PROACTIVE: $_PROACTIVE"
echo "LAKE_INTRO: $_LAKE_SEEN"
echo "TELEMETRY: ${_TEL:-off}"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
mkdir -p ~/.gstack/analytics
open https://garryslist.org/posts/boil-the-oceanWhat does the retro skill do?
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill gstack-retro --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.