retro

Generates weekly engineering retrospectives from Git commit history, author statistics, and code metrics.

127k|19.1k|Updated Mar 11, 2026

Search Tags:#code quality #git #code review #retrospective #engineering metrics #team productivity

Ready to run

npx skills add https://github.com/garrytan/gstack --skill retro-garrytan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive weekly engineering retrospectives, saving valuable time and providing data-driven insights into team productivity and code quality.

Core Features & Use Cases

Automated Data Collection: Gathers commit history, author statistics, and code metrics from Git.
Insightful Analysis: Computes metrics like commit frequency, LOC changes, test coverage, session patterns, and code hotspots.
Team-Aware Reporting: Differentiates contributions between the current user and teammates, offering personalized praise and growth opportunities.
Trend Tracking: Compares current metrics against previous retrospectives to highlight progress and regressions.
Use Case: Run /retro at the end of each week to get a detailed report on what the team accomplished, identify areas for improvement, and celebrate wins, all based on objective data.

Quick Start

Run the retro skill to generate the weekly engineering 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 automate engineering retrospectives using Git history?▼

Automating engineering retrospectives involves analyzing Git commit history and code quality metrics to generate reports. This skill computes commit frequency, tracks author contributions, and identifies work sessions to provide data-driven feedback for continuous team improvement.

What is a data-driven team productivity retrospective?▼

A data-driven team productivity retrospective uses objective Git metrics, such as commit frequency and lines of code changes, to evaluate progress. It differentiates individual contributions, highlights code hotspots, and tracks trends to replace subjective guesses with measurable insights.

Can I generate weekly code review reports for my engineering team?▼

Yes, you can generate weekly code review reports by running the retrospective skill for the last 7 days. It collects author statistics and code metrics to produce team-aware insights, offering personalized praise and identifying specific growth opportunities.

Does this retrospective tool support custom time windows for trend tracking?▼

The retrospective tool supports custom time windows and comparison modes for in-depth analysis. You can compare current metrics against previous periods to highlight progress and regressions, enabling flexible trend tracking beyond the default weekly reporting cycle.

How do code quality metrics factor into automated engineering reports?▼

Code quality metrics factor into automated engineering reports by analyzing commit history and test coverage alongside lines of code changes. This combination identifies code hotspots and session patterns, offering actionable feedback to improve overall team productivity.