retro

Analyze Git repository history to generate engineering retrospectives for defined time windows.

Updated Mar 11, 2026

Search Tags:#git #analysis #metrics #engineering #history #team #retro

Ready to run

npx skills add https://github.com/jkhowland/jkhowland --skill retro-jkhowland

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jkhowland/jkhowland/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/jkhowland/jkhowland --skill retro-jkhowland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retro skill helps engineering teams analyze commits, work patterns, and code quality metrics across a configurable window, providing team-aware praise and growth opportunities with a persistent history.

Core Features & Use Cases

Team-wide analytics: per-author praise and growth opportunities
Windowed retrospectives: last 7, 14, 30 days, compare windows
Persistent history: maintain retros across time with per-commit hotspots
Focus signals: hotspot analysis, PR sizing, pattern detection

Quick Start

Run /retro to generate a weekly engineering retrospective for the past 7 days.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a weekly engineering retrospective from Git commit history?▼

Generate a Git repository retrospective by analyzing commit history over a defined midnight-aligned time window. The analysis reviews commits, tests, hotspots, and focus signals to produce team-aware praise and growth opportunities.

What is team-aware analytics for software engineering retrospectives?▼

Team-aware analytics evaluates per-author and per-file Git metrics to provide individualized praise and growth opportunities. It assesses commits, tests, and hotspots across configurable windows like 7, 14, or 30 days.

Can I compare engineering metrics across different time windows?▼

Yes, you can compare work patterns and code quality metrics across different time windows. The analysis supports comparing retrospectives over the last 7, 14, or 30 days to identify trends and shifts in team focus signals.

Does the retro analysis work with remote Git repositories?▼

The analysis operates on origin/<default> Git history, requiring access to your remote repository's commit data. It extracts per-author metrics, commit hotspots, and focus signals from this remote history.

What additional data sources can I use for Git repository analysis?▼

You can incorporate optional data sources like test files, greptile history, and TODOS.md when present. These sources enrich the engineering retrospective by adding context to commit hotspots and focus signal pattern detection.

How do I maintain a persistent history of engineering retrospectives?▼

You maintain persistent history by running retrospectives consistently across defined time windows. This approach tracks per-commit hotspots and work patterns over time, creating a continuous record of team-wide analytics and focus signals.