retro

Analyze commit history to generate engineering retrospectives with per-author metrics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface actionable learnings from a team's code history to celebrate wins and pinpoint growth opportunities.

Core Features & Use Cases

  • Per-author praise and growth notes based on commit history.
  • Team-wide retros with actionable metrics and trends.
  • Generates a structured retrospective suitable for async review and leadership updates.

Quick Start

Run /retro to generate a seven-day retrospective for your current repo.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective from commit history?

Generate an engineering retro by analyzing a software project's commit history and team contributions. The tool produces per-author praise, growth notes, a leaderboard, and a team-wide health view suitable for async review.

What is a data-driven team retrospective for software engineering?

A data-driven engineering retro analyzes commit history to surface actionable learnings, celebrate team wins, and identify growth opportunities. It outputs per-author metrics, a leaderboard, and a team-wide health view for reports.

Can I run a retrospective for a specific time window like 24 hours or 30 days?

Yes, retrospectives support 24h, 14d, and 30d windows, plus compare windows. The default analyzes the last 7 days of a repository's commit history to generate team contributions and growth metrics.

Does the retrospective tool support cross-project analysis for multiple repositories?

Yes, a global cross-project mode analyzes commit history across multiple repositories simultaneously. This generates a comprehensive engineering retrospective with per-author metrics and a team-wide health view.

What metrics are included in a team-wide engineering retro?

A team-wide engineering retro includes per-author metrics, a per-author leaderboard, and a team-wide health view. These actionable metrics and trends are extracted from commit history to identify growth opportunities.

Is the generated retrospective suitable for leadership presentations?

Yes, the retrospective generates a structured report suitable for async review and leadership updates. It includes actionable metrics, per-author praise, and growth notes formatted for presentation.