retro

Analyze Git history to compute commits, insertions, deletions, and per-author metrics.

Updated Mar 19, 2026

Search Tags:#git #analytics #metrics #engineering #focus #team #retro

Ready to run

npx skills add https://github.com/onlypfachi/chief --skill retro-onlypfachi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/onlypfachi/chief/tree/main/retro
Command: npx skills add https://github.com/onlypfachi/chief --skill retro-onlypfachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are time-consuming and hard to extract useful patterns from raw git data. This Skill automates analysis of commit history, contributor activity, code quality signals, and team patterns to deliver a clear, narrative-focused engineering retrospective.

Core Features & Use Cases

Analyzes commits, insertions/deletions, and per-author contributions over a configurable window.
Generates per-member praise and growth opportunities, including focus and ship highlights.
Produces a narrative and structured metrics report suitable for leadership reviews.

Quick Start

Run the retro for the default 7-day window to get the narrative, metrics, and team insights.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an engineering retrospective from git history?▼

Generating an engineering retrospective from git history involves analyzing commits, insertions, deletions, and per-author metrics to assess team dynamics. It produces a narrative report with an executive summary, highlighting focus hours and suggesting concrete improvements for leadership reviews.

What metrics should I track for a weekly developer team retrospective?▼

Weekly developer retrospectives should track commits, insertions, deletions, and per-author contributions to assess team dynamics. Evaluating these metrics highlights focus hours, session patterns, top contributors, test health, and potential ship-of-the-week items for actionable insights.

Can I analyze individual contributor performance using git commit data?▼

Yes, you can analyze individual contributor performance using git commit data by computing per-author metrics. This analysis highlights individual focus hours, session patterns, top contributors, and specific strengths, generating per-member praise and identifying concrete growth opportunities.

How do I identify engineering focus hours and session patterns from commit history?▼

Identifying focus hours and session patterns from commit history requires analyzing timestamped git activity to map contributor workflows. This reveals peak productivity windows and coding session lengths, helping assess team dynamics, highlight top contributors, and suggest concrete improvements.

Does this retrospective tool work with any git repository?▼

This retrospective tool works by analyzing standard git history within a configurable window, requiring no specific external dependencies. It processes native git data to compute commit metrics and generate narrative reports, making it compatible with standard repository workflows for leadership reviews.