retro

Generate engineering retrospectives from Git commit history with metrics and narrative.

55|8|Updated Jul 21, 2021
One-click install
npx skills add https://github.com/Actual-Chat/actual-chat --skill retro-actual-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Actual-Chat/actual-chat/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/Actual-Chat/actual-chat --skill retro-actual-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives automate the collection and synthesis of a team's engineering activity, turning commit history, code patterns, and contributor signals into actionable insights and a shareable narrative.

Core Features & Use Cases

  • Team-wide retrospective generation from Git history with per-author contributions, trend tracking, and persistent context across weeks.
  • Time-window analysis (7d default with support for 14d, 30d, and compare windows) and a narrative summary suitable for leadership reviews.
  • Optional historical comparison, backlog visibility, and focus metrics to inform planning and improvement conversations.

Quick Start

Run the /retro command to generate this week's retro.

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 commit history?

An engineering retrospective from Git commit history analyzes a team's commits, authors, and code activity to produce actionable insights and a narrative. It turns weekly commit data into a structured JSON retro and a narrative summary suitable for leadership reviews.

What time windows can I use for analyzing team coding activity?

You can analyze team coding activity using 7d, 14d, or 30d windows, with 7d as the default. The tool also supports compare modes to track historical trends and generate focus metrics across the selected commit window.

Does this retrospective tool work with our default Git branch?

Yes, the retrospective tool works with your default Git branch by reading from origin/<default>. It requires no additional dependencies and automatically processes the commit history to generate per-author contributions and trend tracking.

Can I compare historical engineering metrics across different weeks?

Yes, you can compare historical engineering metrics across different weeks using the built-in compare modes. The retrospective output includes optional history and backlog data, enabling persistent context across weeks to inform planning and improvement conversations.

What timezone does the Git commit analysis use for weekly reports?

The Git commit analysis uses Pacific time for all weekly report displays. This ensures consistent time-window boundaries when aggregating commit history and generating per-author contribution metrics for the retrospective narrative.