retro

Analyze Git history to generate weekly engineering retrospectives with team metrics.

Updated Mar 15, 2026

Search Tags:#git #metrics #reporting #team #pulse #retro #work-patterns

Ready to run

npx skills add https://github.com/brianruggieri/claude-personalities --skill retro-brianruggieri

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives can miss subtle patterns in code activity and team dynamics. This Skill analyzes Git history to surface actionable insights about focus, collaboration, and process health.

Core Features & Use Cases

Per-author metrics: commits, LOC, test coverage, and contribution patterns.
Session and time-pattern analysis: peak hours, deep vs micro sessions, and weekly trends.
Narrative-focused highlights: top contributors, strongest ships, and improvement opportunities.

Quick Start

Invoke the retro function with a window argument (e.g., 7d) to generate a weekly engineering retrospective.

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?▼

Generate a weekly engineering retro by analyzing Git history over a configurable window like 7d, 14d, or 30d using origin/main as the baseline. This produces a JSON-ready summary with team-aware insights covering commits, sessions, and focus scores.

What engineering metrics can I track for my team using Git history?▼

You can track per-author Git metrics including commits, insertions, deletions, test coverage, sessions, hotspots, focus scores, PRs, and streaks. These metrics surface actionable insights about collaboration, process health, and individual contribution patterns.

Can I analyze deep work sessions and peak coding hours from Git commits?▼

Yes, session and time-pattern analysis of Git commits identifies peak hours, deep versus micro sessions, and weekly trends. This analysis extracts work patterns directly from commit history to highlight team focus and activity distribution.

Does this Git reporting tool work with any repository branch?▼

This Git reporting tool uses origin/main as the baseline branch for analyzing commit history and generating team metrics. It calculates contributions and work patterns relative to this default branch over a specified time window.

What's the best way to surface improvement opportunities in a sprint retrospective?▼

The best way to surface improvement opportunities is by analyzing Git metrics to produce narrative-focused highlights. This approach identifies top contributors, strongest ships, and process bottlenecks by evaluating commit patterns and focus scores over a configurable window.