retro

Name: retro
Availability: InStock
Author: josephneumann

Analyze Git commit history to generate engineering retrospective reports.

4|Updated Jan 7, 2026

Search Tags:#git #code analysis #metrics #retrospective #developer productivity #commit history

Ready to run

npx skills add https://github.com/josephneumann/claude-corps --skill retro-josephneumann

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the analysis of Git commit history to provide actionable insights into development velocity, work patterns, and code health, helping teams improve their engineering practices.

Core Features & Use Cases

Shipping Metrics: Tracks commits, PRs merged, and lines of code changed.
Work Pattern Analysis: Identifies commit rhythms, session lengths, and peak activity hours.
Code Health: Analyzes commit types, file change hotspots, and PR size distribution.
Trend Tracking: Compares current metrics against historical data for continuous improvement.
Use Case: Run this Skill weekly to review team productivity, identify bottlenecks in the development process, and celebrate significant contributions.

Quick Start

Run the retro skill to analyze the last 7 days of git commit history.

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

To analyze git commit history for engineering retrospectives, this Skill retrieves commit data via Git commands and applies custom logic to compute shipping metrics, work patterns, and code health trends, generating a comprehensive narrative report.

What git metrics can I track to analyze developer productivity?▼

Developer productivity metrics tracked include shipping metrics like commits and PRs merged, work patterns such as commit rhythms and peak activity hours, and code health indicators like file change hotspots and PR size distribution.

Can I compare developer productivity metrics across different time windows?▼

Yes, you can compare developer productivity metrics across different time windows. The Skill supports historical trend tracking, allowing you to compare current metrics against past data to identify continuous improvements or regressions.

Does this retrospective tool require any external dependencies to analyze code health?▼

No external dependencies are required to analyze code health. The Skill operates dependency-free, relying solely on Git commands for data retrieval and custom internal logic for metric computation and trend analysis.

What is the best way to identify file change hotspots and work pattern bottlenecks in git?▼

The best way to identify file change hotspots and work pattern bottlenecks in git is to analyze commit history for code health trends and session lengths. This Skill automates that analysis to pinpoint development friction.