retro

Analyze git commit history to generate weekly engineering retrospectives.

Updated Mar 27, 2026

Search Tags:#git #workflow #analysis #metrics #engineering #team #retro

Ready to run

npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill retro-cenredjun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/retro
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill retro-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros help engineering teams understand commit history, work patterns, and code quality trends by providing persistent history and per-person insights to guide improvements.

Core Features & Use Cases

Automated weekly analytics: analyze git history and activity to surface team-wide and individual patterns.
Per-author insights: identify contributions, praise growth areas, and capture focus areas.
Trend tracking: maintain a persistent history to compare weeks and spot shifts in performance.
Use Case: CTO or senior IC uses it to plan process improvements and mentorship based on historical data.

Quick Start

Type /retro to generate the weekly engineering retrospective for your 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 commit history?▼

Generate a weekly engineering retrospective by analyzing git commit history and coding activity on origin/main. The tool extracts commit data, converts times to Pacific time, and exports metrics like commits, LOC, and tests to a narrative report saved under .context/retros.

Can I analyze individual developer contributions and trends from repository activity?▼

Yes, you can analyze individual developer contributions from repository activity. The retrospective generates per-author insights, identifies focus areas, and highlights growth opportunities for each team member based on their commit history.

Does the weekly retrospective analysis work with any git branch or only origin/main?▼

The weekly retrospective analysis works specifically with repositories tracked on origin/main. It evaluates coding activity within defined time windows like 7, 14, or 30 days to produce trend analyses and per-author insights.

What metrics are included in a git workflow analysis for engineering teams?▼

A git workflow analysis for engineering teams includes metrics such as commits, lines of code, tests, and coding sessions. It maintains persistent history to compare weekly performance shifts and identify team-wide work patterns.

How does persistent history help track engineering team performance over time?▼

Persistent history helps track engineering team performance by saving retrospective reports under .context/retros. This allows you to compare weeks, spot shifts in code quality trends, and plan mentorship based on historical data.

What is the best way to automate weekly analytics for a development team's coding activity?▼

The best way to automate weekly analytics for coding activity is to run the retrospective tool on your repository. It automatically extracts git data, calculates engineering metrics, and produces a narrative report with team-wide patterns and individual insights.