retro

Analyze git history to generate structured weekly retrospectives with per-person contributions.

Updated Aug 23, 2026

Search Tags:#git #analysis #metrics #code-quality #team #retro

Ready to run

npx skills add https://github.com/effiraid/reflix-nextjs --skill retro-effiraid

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are time-consuming and hard to keep consistent. This skill analyzes commit history, work patterns, and code-quality metrics to generate a team-aware retrospective with persistent history and growth insights.

Core Features & Use Cases

Per-person contributions with praise and growth opportunities.
Trend tracking across weeks and persistent history to surface patterns.
Actionable retrospectives that help teams reflect on process, quality, and delivery.

Quick Start

Run the retro skill to generate the latest weekly retrospective for your current repository.

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 git history retrospective analyzes commit logs to produce structured weekly insights on per-person contributions, praise, and growth opportunities. It evaluates work patterns and code-quality metrics to help teams reflect on process, quality, and delivery.

Can I compare code-quality metrics across different time windows for my team?▼

Yes, you can compare code-quality metrics across different time windows. The analysis supports custom comparison windows and cross-project global retros to track trends and surface persistent patterns across multiple weeks.

What is included in a team-aware repository retrospective?▼

A team-aware repository retrospective includes per-author metrics, hotspots, focus signals, and actionable improvements. It highlights individual contributions alongside process and delivery insights to provide structured growth opportunities for the engineering team.

Does the retrospective analysis work for cross-project global retrospectives?▼

Yes, the retrospective analysis supports cross-project global retrospectives. It can analyze git history beyond a single active repository to generate team insights, telemetry controls, and governance prompts across multiple projects.

How do I identify team growth opportunities and praise from commit history?▼

You identify team growth opportunities and praise from commit history by analyzing per-author metrics and work patterns. The retrospective surfaces focus signals and hotspots to highlight actionable improvements and individual contributions for the team.