retro

Analyze weekly Git activity to generate engineering retrospectives with per-author metrics.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/rshelekhov/dotfiles --skill retro-rshelekhov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/rshelekhov/dotfiles/tree/main/claude/skills/gstack/retro
Command: npx skills add https://github.com/rshelekhov/dotfiles --skill retro-rshelekhov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that transform raw Git activity into a structured narrative, helping teams celebrate wins and grow from habits.

Core Features & Use Cases

  • Analyzes commits, authors, and code churn to surface contributions and hotspots.
  • Generates per-person praise and growth opportunities, plus a team-wide narrative.
  • Supports Ship of the Week and focus metrics to highlight high-impact work.

Quick Start

Run /retro to generate the weekly retrospective for the last 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 activity?

Generate a weekly engineering retrospective by running /retro, which analyzes 7-day Git commit history to surface per-author metrics, PR sizing, test discipline, and code hotspots.

What is Git activity analysis for team performance reviews?

Git activity analysis for team performance reviews evaluates commits, code churn, and PR sizing to measure individual contributions and identify code hotspots, producing per-author metrics and a team-wide narrative.

Can I analyze individual developer contributions using Git history?

Yes, you can analyze individual developer contributions using Git history. The tool provides per-author insights, calculating metrics for code churn and PR sizing to generate personalized praise and growth opportunities.

How do I detect code hotspots in a weekly code review?

Detect code hotspots in a weekly code review by analyzing 7-day Git activity and code churn. The tool identifies areas with high modification rates to highlight potential risks in the retrospective.

Does the weekly retrospective support comparing previous Git periods?

Yes, the weekly retrospective supports an optional compare mode for analyzing Git history. This feature contrasts the current 7-day window against previous periods to track team performance.