retro

Generate weekly engineering retrospectives from git commit history and test signals.

8|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/MFS-code/gstack --skill retro-mfs-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/MFS-code/gstack/tree/main/retro
Command: npx skills add https://github.com/MFS-code/gstack --skill retro-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns your repo activity into a clear weekly engineering retrospective so you can understand what shipped, how quality changed, and where to improve.

Core Features & Use Cases

  • Weekly analysis from git history: Summarizes commits, contributors, code churn, and test signals for a chosen time window.
  • Team-aware contributor breakdown: Identifies what each person worked on, when they code, and gives praise + growth opportunities based on observed activity.
  • Trends and stored history: Saves snapshots and compares against the last retro so you can track progress week-over-week.

Quick Start

Invoke the retrospective for the last 7 days by asking for /retro.

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?

A weekly engineering retrospective analyzes repository commit history, contributor activity, and test health signals over a chosen time window. It summarizes commits, code churn, and team productivity automatically.

What is engineering retrospective trend tracking and when do I need it?

Engineering retrospective trend tracking compares current git analytics against prior stored snapshots to measure progress. You need it to understand week-over-week changes in code quality, test health, and team productivity.

Can I run a cross-project engineering retrospective for all my repositories?

Yes, you can run a global cross-project retrospective. When requested, the tool aggregates commit analysis and contributor activity across multiple repositories to provide a unified view of team productivity.

How do I analyze team productivity and contributor activity by time window?

You analyze team productivity by specifying a time window like 24h, 7d, or 30d. The tool computes contributor metrics, identifies what each person worked on, and generates leaderboards with growth opportunities.

Does this commit analysis tool track test health and code quality signals?

Yes, the retrospective tracks test health and code quality signals by evaluating test changes within the git history. It computes these metrics alongside code churn to assess overall repository health.

What are the limitations of git analytics for team productivity measurement?

Git analytics for team productivity measurement relies solely on commit history and code churn, meaning it cannot capture non-code contributions, uncommitted local work, or qualitative engineering context.