retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fghaffar/faystack --skill retro-fghaffar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/fghaffar/faystack/tree/main/retro
Command: npx skills add https://github.com/fghaffar/faystack --skill retro-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often lack a clear, data‑driven view of what they shipped each week, making it hard to spot productivity trends, bottlenecks, or celebrate wins.

Core Features & Use Cases

  • Summarizes commit counts, insertions, deletions, and net LOC for the selected period.
  • Provides per‑author leaderboards, hotspot analysis, and session detection.
  • Includes test coverage, Greptile signal, backlog health, and skill‑usage statistics when available.
  • Generates hourly commit histograms, focus scores, and identifies the “ship of the week.”
  • Works on any Git repository and can be run for custom time windows or global cross‑project retrospectives.

Quick Start

Run /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 report from Git commit history?

Generate a weekly engineering retrospective by running a command against any Git repository to summarize commit history, test coverage, and PR activity into actionable insights. It analyzes work patterns and code quality metrics for a chosen time window automatically.

What engineering metrics are included in a Git repository retrospective?

A Git repository retrospective includes commit counts, insertions, deletions, net LOC, test coverage, and PR activity. It also provides hourly commit histograms, per-author leaderboards, hotspot analysis, session detection, and focus scores.

Can I run an engineering retrospective for a custom time window or multiple projects?

Yes, you can run an engineering retrospective for custom time windows beyond the default 7-day period. The tool also supports global cross-project retrospectives, analyzing contributions and team productivity across multiple repositories.

How do I analyze team productivity and work patterns without manual data collection?

Analyze team productivity by applying the retrospective tool to your Git repository to automatically detect work patterns, session lengths, and focus scores. It identifies bottlenecks and the ship of the week, generating leaderboards without manual data collection.

Does the retrospective analysis require any specific dependencies or components to run?

No specific dependencies or components are required to run the retrospective analysis. It works on any Git repository by directly analyzing the commit history and work patterns to produce tables, leaderboards, and actionable insights.

What's the best way to identify code quality bottlenecks and productivity trends in engineering teams?

The best way to identify bottlenecks is using a data-driven retrospective report that analyzes hotspot activity, Greptile signals, and backlog health. This approach summarizes contributions and team productivity trends to spot issues and celebrate wins.