retro

Analyze Git commits to generate weekly retrospective reports with metrics and trends.

2|Updated Dec 8, 2018

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

Ready to run

npx skills add https://github.com/indykish/dotfiles --skill retro-indykish

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives to synthesize commit history, work patterns, and code-quality metrics into a repeatable, historical narrative used by teams to improve velocity and quality.

Core Features & Use Cases

Automated weekly retrospectives from origin/main commits using configurable time windows (7d, 24h, 14d, 30d) and compare mode.
Rich metrics including commits, LOC, test LOC, active days, sessions, hotspot analysis, and a focus score.
Narrative-style outputs suitable for engineers and executives, with concrete improvements and wins.

Quick Start

Invoke the skill by typing /retro or /retro <window> to generate a retrospective for the specified 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 weekly engineering retrospective from git commits?▼

Yes, you can analyze engineering activity by applying the retro skill to Git repositories with origin/main as the primary branch, using configurable time windows like 7d, 14d, 30d, or 24h to produce retrospective reports.

What metrics are included in a git commit analysis retrospective?▼

Generate retrospective reports with configurable windows like 7d, 14d, 30d, or 24h, and use the optional compare mode to evaluate engineering activity trends and work patterns across different time periods.

Does the weekly retrospective skill work with any git branch?▼

The retrospective skill outputs a narrative-ready summary containing engineering metrics, focus and shipping signals, hotspot analysis, and concrete improvements suitable for both engineers and executives.

Can I compare engineering activity metrics across different time windows?▼

The retrospective skill requires Git repositories using origin/main as the primary branch to fetch commit history, compute metrics, and generate the weekly engineering retrospective report accurately.