One-click install
npx skills add https://github.com/snewhouse/aa-ma-forge --skill retro-snewhouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/snewhouse/aa-ma-forge/tree/main/claude-code/skills/retro
Command: npx skills add https://github.com/snewhouse/aa-ma-forge --skill retro-snewhouse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing clarity after shipping—by turning commit history into an actionable weekly engineering retrospective that highlights progress, quality trends, and team contribution patterns.

Core Features & Use Cases

  • Commit-history retrospective with metrics: Summarizes commits, LOC changes, test coverage, churn, and session patterns over a chosen time window (default 7 days).
  • Team-aware analysis: Identifies the current user vs teammates and produces per-person highlights, including praise and growth opportunities.
  • Quality and focus signals: Detects test discipline, hotspot files, commit-type mix, work session “deepness,” PR size distribution, and a focus score to show where effort concentrated.
  • Optional trend + health reporting: Supports week-over-week comparison for 14d+ windows, includes streak tracking, and factors in Greptile and backlog health when those files exist.

Quick Start

Run the retro skill for the last 7 days by telling your agent: “/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?

Git analytics measures engineering productivity by computing commit metrics, session distributions, and code quality indicators from commit history. It validates command arguments and converts raw git data into actionable insights for recurring reviews.

Can I analyze team productivity and per-author contribution patterns over different time windows?

Yes, you can analyze team productivity over 24h, 7d, 14d, or 30d windows. The analysis identifies current users versus teammates to produce per-person highlights, including praise and growth opportunities based on commit metrics and work session patterns.

What code quality indicators and commit metrics are included in a weekly engineering retrospective?

A weekly engineering retrospective includes commit metrics for test discipline, hotspot files, commit-type mix, PR size distribution, and work session deepness. It computes a focus score to show where engineering effort concentrated during the review window.

Does the retrospective support week-over-week trend comparison and streak tracking?

Yes, week-over-week trend comparison and streak tracking are supported for analysis windows of 14 days or longer. The retrospective optionally factors in Greptile history and TODOS backlog data to generate enriched health reporting metrics when those files exist.

Do I need Greptile history or backlog files to run a git commit analysis retrospective?

No, you do not need Greptile history or TODOS backlog files to run a git commit analysis retrospective. These are optional dependencies that provide enriched metrics and health reporting only when available, while standard commit metadata parsing requires no extra setup.