retro
Weekly engineering retrospective from commit history, with per-person contributions and trends over time.
- Kind
- Skill
- Works with
- Claude Code
- Source
- garrytan/gstack @ 01593aa67c94
- Path
- retro/SKILL.md
- License
- MIT
- Jobs
- Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run gen:skill-docs --> ## When to invoke this skill Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. ## Preamble (run first) ```bash _SS="$HOME/.claude/skills/gstack/bin/gstack-skill-start" [ -x "$_SS" ] || _SS=".claude/skills/gstack/bin/gstack-skill-start" "$_SS" --skill "retro" --model "claude" --parent-pid "$PPID" \ || echo "SKILL_START: unavailable — stale install; run ./setup or /gstack-upgrade (preamble degraded, continue the user's task)" ``` Read the echoed `KEY: value` STATUS lines — they drive every preamble rule below. **Degraded mode:** if `SKILL_START_PROTO: 1` is missing from the output (script absent, stale install, or a different protocol number), apply safe defaults: treat `SESSION_KIND` as `interactive`, do NOT assume Conductor, …