retro

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

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill retro-timurgaleev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/retro
Command: npx skills add https://github.com/timurgaleev/vibestack --skill retro-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are critical for aligning teams, but capturing and synthesizing commit history, code quality signals, and contributor growth across time is error-prone and time-consuming. This Skill automates the collection and curation of engineering activity, producing a structured, narrative retrospective with measurable metrics and actionable insights.

Core Features & Use Cases

  • Automated collection of commit history within a rolling window.
  • Per-person contribution breakdown and growth-oriented analysis.
  • Trend-aware storytelling with metrics that tie outcomes to improvements.
  • Cross-repo retrospectives and week-over-week comparisons (when available).

Quick Start

Invoke the retro by typing /retro to generate this week's engineering retrospective.

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

You can generate a weekly engineering retro by running /retro, which collects git commit history, estimates LOC changes, identifies hotspots, and synthesizes a narrative retrospective with growth-oriented recommendations.

What is an automated engineering retro and how does it analyze team activity?▼

An automated engineering retro analyzes git commits, code changes, and quality signals within a time window to produce per-person contribution breakdowns, trend analysis, and growth-oriented recommendations.

Can I run a cross-repo retrospective comparing week-over-week engineering metrics?▼

Yes, the retro workflow applies to individual repositories or across multiple projects, supporting cross-repo retrospectives and week-over-week trend comparisons to track engineering growth over time.

Does the retrospective analysis require any external dependencies or components?▼

No external dependencies or components are required; the retro performs end-to-end data collection directly from git history with built-in safety checks and graceful fallbacks for missing data.

What happens if git history is incomplete or missing during the retrospective generation?▼

The retrospective workflow includes safety checks and graceful fallbacks, ensuring that if git history is incomplete or data is missing, the narrative generation still produces a valid retrospective output.