retro

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

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill retro-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/westkite1201/garden-engine --skill retro-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams and solo developers lack a data-driven view of what actually shipped each week, how work patterns look, 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 feedback. ## Core Features & Use Cases - Commit & Metrics Analysis: Aggregates commits, LOC, test ratios, PR sizes, hotspots, and commit-type breakdowns over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdowns: Identifies each contributor, highlights praise anchored in real commits, and suggests growth opportunities based on data. - Trend & Streak Tracking: Compares against prior saved retros, tracks shipping streaks, and supports a cross-project global mode across AI coding tools. - Use Case: At the end of a sprint, run the retro to get a leaderboard of contributions, a focus score, the ship of the week, and week-over-week test ratio trends without manually digging through git log. ## Quick Start Ask the assistant 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 the retro skill with a time window argument such as 7d, 14d, or 24h. It queries git log on the default branch, computes commit, LOC, test ratio, and session metrics, then outputs a formatted retrospective with per-author breakdowns.

How does the retro skill analyze team contributions?

It identifies the current user via git config, then groups commits by author. Each contributor gets commits, LOC, focus areas, commit-type mix, session patterns, test ratio, plus specific praise and one growth suggestion anchored in actual commit data.

Can I compare this week's engineering metrics against last week?

Yes, use the compare argument to evaluate the current window against the prior same-length window. The skill also loads previously saved retro snapshots from .context/retros to show deltas in test ratio, sessions, and other key metrics.

Does the retro skill work outside a git repository?

The standard repo-scoped retro requires a git repository, but the global mode runs a cross-project retrospective across all AI coding tools without needing to be inside a repo. Global mode accepts an optional time window argument.

What time windows does the engineering retro support?

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