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 retro-jovieinc-jovie --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 comprehensive weekly retrospective by analyzing commit history, work patterns, and code quality metrics. Identifies the user running the retro and then analyzes every contributor with per-person praise and growth opportunities. Designed for Claude Code users at senior IC/CTO level.
How it works
The skill parses the /retro command with optional time-window arguments to determine a 7, 24h, 14d, or 30d window (default 7 days). It computes midnight-aligned start dates for day/week units and uses git log queries with explicit --since timestamps. It fetches origin, identifies the current user, and then analyzes contributors, producing per-person praise and growth opportunities. It supports a compare mode to contrast current vs prior windows. It requires parsing arguments, calculating start dates, and running git commands like git log with --since and related filters. The exact steps include validating the argument, computing the window, gathering data, and formatting a report that highlights individual contributions and areas for improvement.
When to use it
Use when the user issues the /retro command (default last 7 days) to generate a weekly retrospective. Optional: /retro 24h, /retro 14d, /retro 30d, or /retro compare variants to compare windows.
What it can touch
This skill touches git data via commands like git fetch origin <default> --quiet and git log with --since, reads repository history, and analyzes per-contributor metrics. It requires access to the local git repository and network to fetch origin.
Caveats
The skill description specifies handling local time zones and midnight-aligned windows, and explicit formatting for --since dates. It relies on correct detection of the repository default branch name and the current user. It does not guarantee specific outcome quality; outputs depend on repository history and provided time window. License is MIT (as per frontmatter).
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs --> ## Preamble (run first) ```bash _UPD=$(~/.claude/skills/gstack/bin/gstack-update-check 2>/dev/null || .claude/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=$(~/.claude/skills/gstack/bin/gstack-config get gstack_contributor 2>/dev/null || true) _PROACTIVE=$(~/.claude/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=$(~/.claude/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 retro-jovieinc-jovie --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.