retro

Name: retro
Availability: InStock
Author: Florian

Analyze commit history and code quality signals to generate team retrospectives.

4|2|Updated Mar 29, 2026

Search Tags:#git #analysis #metrics #engineering #team #retro

Ready to run

npx skills add https://github.com/florianhorner/mammamiradio --skill retro-florianhorner

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes commit history, work patterns, and code quality signals to produce a team-aware weekly retrospective that highlights growth areas and successes.

Core Features & Use Cases

Analyzes project history to surface trends in contribution, quality, and delivery across the team.
Generates proactive retrospectives at the end of each sprint, suggesting concrete improvements.
Provides per-person breakdowns to highlight individual contributions and development opportunities.

Quick Start

Ask Claude to run a weekly retro on your repository to generate a team-focused retrospective summary.

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 retrospective from git commit history?▼

Analyze commit history, work patterns, and code quality signals to generate a team-aware weekly retrospective, surfacing per-person contributions and suggested focus areas.

What is a team-aware sprint retrospective based on repository metrics?▼

A team-aware sprint retrospective uses project history and code quality signals to surface contribution trends, delivery patterns, and per-person development opportunities across the team.

How do I get per-person contribution breakdowns for my weekly sprint?▼

Analyze commit history and work patterns to highlight individual contributions, development opportunities, and growth areas for each team member.

Do I need persistent history storage to run automated retrospectives on repository data?▼

Yes, generating proactive summaries and recommended focus areas requires access to repository data and persistent history storage to track trends over time.

Can I use commit analysis to suggest concrete improvements for my engineering team?▼

Yes, evaluating code quality signals and work patterns generates proactive retrospectives that suggest concrete improvements at the end of each sprint.

What's the best way to analyze code quality signals for project retrospectives?▼

Combine commit history and work pattern analysis to identify delivery trends, per-person contributions, and recommended focus areas for project retrospectives.