retro

Generates weekly engineering retrospectives from git commit history with per-contributor metrics and trend tracking.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/VertaKhan/cs_gstack --skill retro-vertakhan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/VertaKhan/cs_gstack/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/VertaKhan/cs_gstack --skill retro-vertakhan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack visibility into what actually shipped each week, how work patterns affect output, and whether code quality is trending up or down. This Skill turns raw git history into a structured retrospective with metrics, session analysis, and per-person breakdowns. ## Core Features & Use Cases - Commit and Metrics Analysis: Aggregates commits, PRs, insertions, deletions, test LOC ratio, and active days over a configurable window (24h, 7d, 14d, 30d). - Work Pattern Detection: Builds hourly commit histograms, detects coding sessions using a 45-minute gap threshold, and classifies deep, medium, and micro sessions. - Team-Aware Breakdowns: Identifies the current user via git config and produces a per-author leaderboard with focus areas, commit type mix, praise, and growth opportunities. - Use Case: At the end of a sprint, run /retro compare 14d to see how this period's shipping velocity, fix ratio, and test coverage compare against the prior two weeks. ## Quick Start Ask the AI to run a weekly engineering retrospective over the last 7 days of this repository's commit history.

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 history?▼

Run /retro to analyze the last 7 days of commits on the default branch. It gathers git log data, computes metrics like commits, LOC, and test ratio, then produces a summary table, session analysis, and per-contributor breakdown.

How to compare engineering output between two time periods?▼

Use /retro compare to contrast the current window against the prior same-length window, or /retro compare 14d for an explicit window. The output highlights changes in velocity, fix ratio, and test coverage between periods.

Can I run a retrospective across multiple projects?▼

Yes, /retro global runs a cross-project retro across all AI coding tools without requiring a git repo. It defaults to 7 days, and /retro global 14d sets an explicit window.

What time windows does the retro command support?▼

Supported windows are hours (24h), days (7d, 14d, 30d), and weeks (2w). Day and week units align to local midnight, while hour units use relative offsets. Invalid arguments print a usage message and stop.

Why does the retro show a high fix ratio warning?▼

A fix ratio above 50 percent of conventional commits signals a ship-fast-fix-fast pattern that may indicate review gaps. The skill flags this in the commit type breakdown so teams can investigate root causes.