retro

Analyze commit history and team activity to generate engineering retrospectives.

Updated Mar 19, 2026

Search Tags:#git #metrics #engineering #code-quality #team #retro

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze commit history and team activity to produce a comprehensive engineering retrospective with per-person praise and growth opportunities.

Core Features & Use Cases

Team-aware retrospectives that identify individual contributions and growth areas.
Metrics-driven narrative including commits, LOC, PRs, test health, hotspots, and session patterns.
Save and compare retrospectives over time, with per-author breakdowns and focused storytelling.

Quick Start

Run /retro to generate a weekly retrospective for the default 7-day window and see a narrative report.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a team retrospective from git commit history?▼

Generate a team retrospective by analyzing git commit history to produce a comprehensive report of team activity. The retrospective covers commits, LOC, PRs, test health, hotspot analysis, and per-author breakdowns for the specified period.

What is included in a code quality retrospective for engineering teams?▼

A code quality retrospective includes metrics-driven narratives with per-author breakdowns, focus scores, and trend comparisons. It collects commits, LOC, test health, hotspot analysis, and session patterns to identify individual contributions and growth areas.

Can I compare engineering metrics retrospectives over time?▼

Yes, you can compare engineering metrics retrospectives over time using comparison mode. The system persists history, allowing you to save retrospectives and compare team-wide focus scores, trends, and per-author contributions across different periods.

Does the retrospective analysis support sprint periods longer than a week?▼

Retrospective analysis supports weekly sprints and any period up to 30 days. You can adjust the default 7-day window to analyze longer team activity cycles, capturing commit history and engineering metrics for the entire duration.

What is the best way to analyze individual developer contributions from git history?▼

The best way to analyze individual developer contributions is generating a team-aware retrospective that parses git history. It provides per-author breakdowns, highlighting individual contributions and suggesting growth opportunities within the metrics-driven narrative.

Are there limits to the commit history window for a team-wide retrospective?▼

The commit history window for a team-wide retrospective is limited to a maximum of 30 days. For the default weekly sprint, the system analyzes a 7-day window; exceeding the 30-day limit requires breaking the analysis into smaller periods.