retro

Name: retro
Availability: InStock
Author: jonolsenca

Aggregate git commit history into weekly team retrospectives with per-person metrics.

Updated Aug 27, 2026

Search Tags:#git #workflow #metrics #engineering #code-quality #team #retro

Ready to run

npx skills add https://github.com/JonOlsenCa/gstack-main --skill retro-jonolsenca

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with historical context to reveal trends, praise, and growth opportunities.

Core Features & Use Cases

Analyze team contributions across the sprint to surface per-person praise and growth areas.
Track long-term patterns in shipping velocity, code quality, and collaboration to inform process improvements.
Proactively surface action items at week end and tailor recommendations for future sprints.

Quick Start

Run /retro to generate a weekly engineering retrospective for the current repository.

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

Generate a weekly engineering retrospective by analyzing git commit history, work patterns, and code quality metrics to track shipping velocity and contributor contributions. Run the /retro command to aggregate repository data and output a structured review.

Can I analyze code quality metrics across multiple projects for a team retrospective?▼

Yes, team retrospectives can analyze code quality metrics and work patterns across one repo or multiple projects. The analysis provides per-person breakdowns of contributor contributions and identifies growth opportunities for the engineering team.

What is a git commit history retrospective and how does it track engineering trends?▼

A git commit history retrospective aggregates commit data to compute metrics, track shipping velocity trends, and surface process improvements. It analyzes historical context to reveal long-term patterns in code quality and collaboration for engineering teams.

How do I track shipping velocity and contributor contributions for my engineering team?▼

Track shipping velocity and contributor contributions by computing metrics from git history to generate a team-focused retrospective. The analysis provides per-person breakdowns, historical trend tracking, and tailored recommendations for future sprints.

Does the weekly retrospective analysis work with a single repository or do I need multiple projects?▼

Weekly retrospective analysis works with both a single repository and multiple projects. It reads git history from the configured scope and aggregates commit data to compute shipping velocity, code quality, and collaboration metrics for the team.

What action items does a git history retrospective surface for future sprints?▼

A git history retrospective proactively surfaces action items at week end by analyzing work patterns and code quality metrics. It provides tailored recommendations for future sprints and identifies growth opportunities for individual contributors.