retro

Analyze git commit history into team-aware retrospective metrics and recommendations.

Updated Mar 21, 2026

Search Tags:#git #analysis #metrics #team #retro

Ready to run

npx skills add https://github.com/TimHL5/carousel --skill retro-timhl5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/TimHL5/carousel/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/TimHL5/carousel --skill retro-timhl5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams understand commit history, work patterns, and code quality trends, turning raw data into actionable feedback for continuous improvement.

Core Features & Use Cases

Analyzes commit history, per-person contributions, and metrics to reveal growth opportunities and praise.
Maintains a persistent history of retros with trend tracking and team-aware insights.
Use cases include weekly retros, post-sprint reflections, and reviews of "what did we ship" across the team.

Quick Start

Invoke /retro to generate a weekly engineering retrospective for the default 7-day window.

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

To generate a weekly engineering retrospective, the tool analyzes your repository's git commit history within a configurable time window, defaulting to 7 days, and summarizes team metrics, per-author focus, and actionable recommendations.

What metrics are included in a git commit analysis for team retros?▼

Git commit analysis for retros includes metrics such as commit counts, lines of code changed, pull request activity, test health, and per-author focus to provide team-aware insights and highlight growth opportunities.

Can I analyze cross-project git history for a team retrospective?▼

Yes, you can analyze cross-project git history by operating in global cross-project mode, which aggregates commit data across repositories to generate a comprehensive team retrospective with per-person praise.

How do I track engineering trends over multiple sprints using git data?▼

You can track engineering trends over multiple sprints because the tool maintains a persistent history of retrospectives, allowing you to compare git metrics, work patterns, and code quality trends over time.

Does the retrospective analysis require a specific repository setup?▼

Retrospective analysis requires access to your repository's git commit history and pull request data to evaluate test health and author contributions, needing no additional dependencies or complex environment setup.