retro

Analyze Git commit history to generate a team retrospective with per-author insights.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill retro-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill retro-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill generates a structured, team-focused retrospective that analyzes commit history, work patterns, and code quality, delivering insights with per-person praise and growth opportunities.

Core Features & Use Cases

  • Persistent history and trend tracking of contribution patterns across the team.
  • Per-person praise and growth guidance, with inline recommendations for improvements.
  • Proactive synthesis of metrics like commits, insertions, deletions, hotspots, and quality signals to guide weekly planning.

Quick Start

Ask Claude to run /retro for the default 7-day window to generate the latest retrospective insights.

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 retrospective from Git commit history?

You can generate a weekly retrospective from Git commit history by running the /retro command, which analyzes a default 7-day window to produce structured team insights including per-author praise and growth opportunities.

What metrics are included in a Git repository analytics retrospective?

A Git repository analytics retrospective includes commits, insertions, deletions, hotspots, a per-user leaderboard, and quality signals, synthesizing these metrics to guide weekly planning and team growth.

Can I track team contribution patterns and growth over time using Git analytics?

Yes, you can track team contribution patterns using Git analytics because the retrospective maintains a persistent history with trend analyses, tracking contribution patterns across the team over time.

Does the Git retrospective provide individual feedback for developers?

Yes, the Git retrospective provides individual feedback for developers by delivering per-person praise and growth guidance with inline recommendations for improvements based on their commit history.

How do I identify code hotspots and work patterns from repository commits?

You can identify code hotspots and work patterns from repository commits through the retrospective's proactive metric synthesis, which highlights hotspots and contribution patterns to guide weekly planning.