retro

Generate engineering retrospectives from git history and metrics.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Jaykaijack/openclaw-backup --skill retro-jaykaijack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Jaykaijack/openclaw-backup/tree/main/skills/gstack/retro
Command: npx skills add https://github.com/Jaykaijack/openclaw-backup --skill retro-jaykaijack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a comprehensive, team-aware engineering retrospective by analyzing git commit history, test and code churn, session patterns, and repository metadata so leaders can understand what shipped, who contributed, and where attention is needed.

Core Features & Use Cases

  • Aggregates commits, insertions, deletions, PR references, and per-author contributions for a chosen time window.
  • Detects work sessions, hourly commit distributions, hotspots, PR size buckets, test health, streaks, and week-over-week trends.
  • Generates per-contributor praise and growth suggestions, identifies the ship of the week, and saves a JSON snapshot for trend comparisons.
  • Use cases: weekly team reviews, post-sprint summaries, release readiness checks, and manager/CTO-level audits.

Quick Start

Invoke /retro to generate a 7-day engineering retrospective that analyzes commits, tests, hotspots, and contributors and saves the result to .context/retros.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an engineering retrospective from git commit history?

You can generate an engineering retrospective by analyzing git commit history, test changes, and code churn to produce team-aware insights. This process aggregates commits, insertions, deletions, and per-author contributions for a chosen time window.

What metrics are included in a git repository engineering retrospective?

An engineering retrospective includes commits, insertions, deletions, PR references, test health ratios, hotspot analysis, and per-author contributions. It also detects work sessions, hourly commit distributions, PR size buckets, and week-over-week trends.

How do I analyze contributor activity and code churn for a sprint review?

Analyze contributor activity and code churn by running git queries against the default origin branch to compute per-author commits, insertions, and deletions. The retrospective detects work sessions and generates per-contributor praise and growth suggestions.

Does this retrospective tool require access to a specific default branch?

Yes, this retrospective tool requires the ability to run git queries against origin/<default>. It also reads local gstack analytics and TODOS to compute metrics like test ratios and session patterns for the chosen time window.

What is the best way to track week-over-week engineering trends in a repository?

Track week-over-week engineering trends by saving JSON snapshots to .context/retros after each analysis. Comparing these snapshots allows leaders to monitor changes in commits, test health, hotspots, and contributor activity over time.