retro

Analyze git commit history to generate weekly engineering retrospectives with per-person praise.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill retro-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill retro-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives help teams reflect on their engineering work, surface praise and growth opportunities, and track progress over time.

Core Features & Use Cases

  • Per-contributor analysis with praise and growth opportunities
  • Time-window based retro over git history, hotspots, test health, backlog and focus metrics
  • Generates a narrative plus a structured snapshot for record-keeping

Quick Start

Run /retro to generate a weekly engineering retrospective for your last 7 days with per-person praise and growth opportunities.

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 commit history?

You can generate a weekly engineering retrospective by analyzing team git commit history to compute LOC, hotspots, test health, and focus metrics. The tool outputs a narrative with per-person praise and growth opportunities alongside a structured JSON snapshot.

What engineering metrics can I extract from git history for a team retro?

Git history retro analysis extracts commits, lines of code, hotspots, test health, backlog, and focus metrics. These metrics are aggregated over a configurable time window to build a team-aware narrative for your retrospective.

Can I analyze individual contributor performance during a code quality retrospective?

Yes, the retrospective provides per-contributor analysis by extracting commit data from git history. It generates specific praise and growth opportunities for each team member while preserving privacy and handling missing data gracefully.

Does the git retrospective support custom time windows and historical comparison?

The git retrospective operates on a configurable time window for your analysis and supports historical comparison. It preserves persistent history by outputting a structured JSON snapshot that can be tracked over time.

What happens if git commit data is missing when generating team metrics?

The retrospective analysis handles missing git data gracefully without breaking the workflow. It aggregates available commits, LOC, and test health metrics to generate the most comprehensive narrative possible for your team.