retro

Analyze git commit history to generate data-driven weekly retrospective reports.

48|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/g4rcez/dotfiles --skill retro-g4rcez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/retro
Command: npx skills add https://github.com/g4rcez/dotfiles --skill retro-g4rcez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retros often lack structured, data-driven insights. This skill analyzes origin/<default> commit history, team contributions, and code quality patterns to generate a repeatable retrospective that surfaces praise and growth opportunities for every contributor.

Core Features & Use Cases

  • Generates a team-aware retrospective with per-author contributions, time-window analytics, and narrative guidance.
  • Computes core metrics (commits, insertions, deletions, PRs, hotspots, test proxies) and surfaces growth opportunities.
  • Supports a compare mode to quantify week-over-week changes and long-term trends, and can include backlog/greptile data when available.

Quick Start

Run /retro in your repository to generate a weekly engineering retrospective for the last 7 days (extend with 24h, 14d, or 30d as needed).

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a data-driven weekly engineering retrospective from git commit history?

Generate a data-driven weekly engineering retrospective by analyzing origin/<default> commit history to surface team contributions, work patterns, and code quality trends. Run /retro in your repository to produce a structured JSON snapshot and narrative for the last 7 days.

Can I compare week-over-week engineering metrics for my team?

You can compare week-over-week engineering metrics using the compare mode to quantify changes and long-term trends. The retrospective evaluates team contributions, commits, insertions, deletions, and PRs across your selected time window.

What git data is needed to run a team engineering retrospective?

Running a team engineering retrospective requires git data from the default branch, specifically origin/<default> commit history. The skill converts timestamps to Pacific time and analyzes per-author contributions within the specified time window.

How does a git-based retrospective identify team improvement opportunities?

A git-based retrospective identifies improvement opportunities by computing core metrics like commits, insertions, deletions, PRs, hotspots, and test proxies. It surfaces growth opportunities and narrative guidance for every contributor in the selected time window.

Can I use a 30-day time window instead of 7 days for an engineering retro?

You can extend the engineering retro time window beyond the default 7 days by specifying 24h, 14d, or 30d. The retrospective analyzes all contributor activity and commit history within your chosen duration.

Does the weekly retro support integrating backlog and code quality data?

The weekly retro supports optional backlog and greptile data integration when available. Including this data enriches the code quality trend analysis and structured JSON snapshot output.