retro

Analyze origin/main commits to compute activity, LOC changes, and contributor metrics.

5|2|Updated Mar 1, 2026

Search Tags:#git #productivity #analysis #metrics #engineering #teamwork #retro

Ready to run

npx skills add https://github.com/umairinayat/Specter-AI --skill retro-umairinayat

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of comprehensive engineering retrospectives by aggregating commit data, metrics, and team signals to reveal patterns, focus, and opportunities.

Core Features & Use Cases

Automated data collection: gathers commit history, per-author stats, and hotspot files to compute actionable metrics.
Per-author insights: surfaces top focus areas, work patterns, and growth opportunities for each contributor.
Narrative retros: produces a structured narrative including focus score, ship of the week, team wins, and concrete next steps.
Planning and forecasting: informs weekly planning by highlighting trends, bottlenecks, and allocation opportunities.

Quick Start

Run /retro to generate the current week's engineering retrospective using 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 data-driven engineering retrospective from git commits?▼

To generate an engineering retrospective, run the retro command to analyze the latest commits on origin/main. It computes overall activity, LOC changes, contributor counts, and per-author breakdowns to produce a structured narrative for your team.

What engineering metrics are included in an automated team retrospective?▼

An automated team retrospective includes commit-type distribution, hotspot files, session patterns, focus scores, and ship metrics. It also provides per-author insights and a team narrative interpreting the data to highlight trends and growth opportunities.

Can I compare current engineering activity metrics with a previous retrospective?▼

Yes, you can compare current engineering activity metrics with a previous retrospective. The output includes a comparison option if a prior retro exists, allowing you to track trends and identify shifts in contributor focus or LOC changes over time.

How do I analyze contributor focus and work patterns from git history?▼

You can analyze contributor focus and work patterns by evaluating per-author breakdowns from your git history. The analysis surfaces top focus areas, work session patterns, and growth opportunities for each contributor based on their commit activity.

Does the retrospective analysis require any specific git branch setup?▼

The retrospective analysis requires access to the origin/main branch to gather commit history and compute metrics. It analyzes the latest commits within a specified 7-day window by default to ensure consistent and accurate weekly reporting.

What is the best way to summarize weekly engineering team output for planning?▼

The best way to summarize weekly engineering team output is to aggregate commit data into a structured narrative. This approach highlights team wins, ship of the week, and concrete next steps, directly informing your weekly planning and resource allocation.