retro

Generates weekly engineering-retro metrics and narratives from git history.

11|1|Updated Feb 7, 2026

Search Tags:#git #workflow #metrics #retrospective #engineering #team

Ready to run

npx skills add https://github.com/KSD-CO/IronCode --skill retro-ksd-co

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/KSD-CO/IronCode/tree/main/packages/ironcode/skills/retro
Command: npx skills add https://github.com/KSD-CO/IronCode --skill retro-ksd-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams struggle to turn raw git history into actionable, time-bound insights that inform planning and process improvements.

Core Features & Use Cases

Data-driven retrospectives: compile commits, LOC, test activity, and per-author contributions.
Focus & patterns: identify peak hours, hotspots, and session dynamics to inform process changes.
Ship-of-the-week: highlight the most impactful change in the window and rationale.
Narratives: generate a concise team-level interpretation and actionable takeaways.

Quick Start

Run the retro for the default 7-day window to generate metrics, a narrative, and a .context/retros JSON snapshot.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate data-driven engineering retrospectives from git history?▼

Engineering retrospectives from git history are generated by detecting the default branch and gathering commits within a retro window to aggregate metrics like LOC, test activity, and per-author contributions. This produces a JSON snapshot and a concise team-level narrative with actionable takeaways.

What metrics are included in a git commit history analysis for team retrospectives?▼

Team retrospective metrics from git commit history include commits, LOC, test activity, per-author contributions, hourly activity, hotspot files, commit types, and PR sizes. The analysis also parses Co-Authored-By trailers to accurately attribute pair programming work.

How can I track per-author contributions and session dynamics from git commits?▼

Tracking per-author contributions and session dynamics from git commits involves aggregating commits within a time window and parsing Co-Authored-By trailers. This identifies individual contribution levels, peak working hours, and session patterns to inform process improvements.

Can I compare current engineering metrics with the previous week's retro?▼

Comparing current engineering metrics with the previous week's retro is supported by generating a current JSON snapshot and narrative that includes comparisons to the prior retro when available. This highlights trends in commits, LOC, and test activity over time.

What is a Ship of the Week highlight in a development team retrospective?▼

A Ship of the Week highlight in a development team retrospective identifies the most impactful change within the analysis window and provides the rationale for its significance. It draws directly from aggregated git metrics to focus team attention on high-value deliverables.

Do I need any specific dependencies to run a git workflow retrospective?▼

No specific dependencies are required to run a git workflow retrospective. The process operates directly on git history to detect the default branch, gather commits, and aggregate metrics into a JSON snapshot and narrative without external tool dependencies.