retro

Generate weekly or cross-project engineering retrospectives from git history and contributor activity.

Updated Mar 28, 2026

Search Tags:#git #analytics #metrics #retrospective #code-quality #contributions

Ready to run

npx skills add https://github.com/24601/gastack-pre-fork --skill retro-24601

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/24601/gastack-pre-fork/tree/main/retro
Command: npx skills add https://github.com/24601/gastack-pre-fork --skill retro-24601

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retro skill automates the collection and synthesis of engineering history — turning commit data, participation, and quality signals into an actionable weekly or cross-project retrospective.

Core Features & Use Cases

Per-person praise and growth opportunities extracted from contributions
Persistent history, trend tracking, and team-aware narratives for weekly sprints or multi-project retros
Global retro mode across multiple AI coding tools

Quick Start

Run /retro to generate a weekly or global retrospective for the current project.

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 retro skill summarizes your repository's git history and contributor activity, extracting per-person contributions and quality signals into a structured narrative. It requires access to local git history and project analytics data.

What is a multi-repo retrospective and how does cross-project git analysis work?▼

A multi-repo retrospective analyzes contributor activity and commit data across multiple repositories simultaneously. The retro skill's global mode synthesizes cross-project engineering history to highlight patterns and growth opportunities across your entire codebase.

Can I use git analytics to track per-person contributions and growth opportunities for sprint reviews?▼

Yes, git analytics can track per-person contributions and growth opportunities for sprint reviews. The retro skill extracts participation data and quality signals from commit history to produce team-aware narratives and persistent trend tracking for sprint-end reviews.

Do I need local git history and telemetry data to run an automated code retrospective?▼

You need access to local git history and project analytics data to run an automated code retrospective. Optional telemetry can also be integrated to enhance the structured metrics and narrative output for leadership reviews.

What's the best way to summarize contributor activity patterns across multiple AI coding tools?▼

The best way to summarize contributor activity patterns across multiple AI coding tools is using a global retro mode. This approach analyzes cross-project engineering history to produce team-aware narratives that highlight participation trends and growth opportunities.

Why does my engineering retrospective need persistent history and trend tracking?▼

Your engineering retrospective needs persistent history and trend tracking to identify long-term patterns in contributor activity and code quality. This enables team-aware narratives that reveal growth opportunities and participation trends across weekly sprints or multi-project reviews.