retro

Analyze Git history and code quality signals to generate engineering retrospectives.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/gaaschk/gaasch-family --skill retro-gaaschk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/gaaschk/gaasch-family/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/gaaschk/gaasch-family --skill retro-gaaschk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives that analyze commit history, work patterns, and code quality metrics to surface praise and growth opportunities for team members, with persistent history.

Core Features & Use Cases

  • Team-aware per-person contributions with growth areas and praise
  • Analyzes commits, insertions/deletions, test signals, hotspots, and overall code health
  • Produces a structured recap suitable for planning and improvement

Quick Start

Run the retro skill to generate a weekly summary from the last 7 days and optionally compare with the prior window.

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

Generate an engineering retrospective by analyzing a 7-to-30-day window of git history and code quality signals. The tool produces a narrative report with quantitative metrics, including commits, lines of code, and test signals.

Can I analyze per-author code contributions and growth areas from git metrics?

Yes, you can analyze per-author code contributions to highlight individual praise and growth opportunities. It evaluates commit history, insertions, deletions, and code hotspots to provide a team-aware per-person breakdown.

How do I compare engineering metrics across different time windows?

Compare engineering metrics across different time windows by applying the analysis to 7d, 14d, 30d, or compare modes. This generates a structured recap showing quantitative differences in commits, tests, and code health.

What code quality signals are included in a git analytics retrospective?

A git analytics retrospective includes code quality signals such as test signals, code hotspots, insertions, deletions, and overall code health. These metrics are aggregated into a clear table and executive summary.

Does the weekly retrospective output support JSON format for reporting?

Yes, the weekly retrospective output supports a JSON snapshot or report format. The structured recap includes a concise executive summary, metric tables, and per-author breakdowns suitable for planning.

What is the best way to run a team-aware weekly code retrospective?

The best way to run a team-aware weekly code retrospective is to analyze the last 7 days of git history and optionally compare it with the prior window. This surfaces work patterns and code quality metrics for team improvement.