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-caraseli02-moldovadirect --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 engineering retrospective analyzing commit history, work patterns, and code quality metrics. Identifies the user running the command, then analyzes every contributor with per-person praise and growth opportunities.
How it works
The skill is invoked via the /retro command with optional time window arguments (e.g., 24h, 14d, 30d, compare). It defaults to the last 7 days. It computes an absolute start date aligned to local midnight for day/week units and uses explicit --since timestamps in git commands. It gathers data using a sequence of git commands run in parallel to collect:
- All commits in the window with timestamps, subject, hash, author, and stats
- Per-commit test vs production LOC breakdown by author
- Commit timestamps for session detection and hourly distribution
- Files most frequently changed (hotspots)
- PR numbers mentioned in commit messages
- Per-author file hotspots
- Per-author commit counts
The commands to run include:
git fetch origin <default> --quietgit config user.nameandgit config user.emailgit log origin/<default> --since="<window>" --format="%H|%aN|%ae|%ai|%s" --shortstatgit log origin/<default> --since="<window>" --format="COMMIT:%H|%aN" --numstatgit log origin/<default> --since="<window>" --format="%at|%aN|%ai|%s" | sort -ngit log origin/<default> --since="<window>" --format="" --name-only | grep -v '^$' | sort | uniq -c | sort -rngit log origin/<default> --since="<window>" --format="%s" | grep -oE '#[0-9]+' | sed 's/^#//' | sort -n | uniq | sed 's/^/#/'git log origin/<default> --since="<window>" --format="AUTHOR:%aN" --name-onlygit shortlog
The skill emphasizes team-aware analysis, breaking down results per person and offering praise and growth opportunities for each contributor.
When to use it
Use when asked for a weekly retro or an engineering retrospective report. It also notes that it proactively suggests at the end of a work week or sprint.
What it can touch
Commands reference Bash environment and standard git tooling. The skill lists allowed-tools as Bash, Read, Write, Glob, AskUserQuestion. The described data gathering steps rely on Bash and Git; no explicit external scripts are listed beyond standard git commands.
Caveats
No explicit limitations or licensing notes beyond the overall skill metadata (MIT license). The description indicates per-person analysis and growth areas, but the exact outputs or reporting format are not specified in the provided excerpt.
<!-- 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
- 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
- Step 3: Commit Time Distribution
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-caraseli02-moldovadirect --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.