retro

Analyzes weekly engineering activity from commit history, PR cadence, and quality signals to produce a retrospective.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/legotec73/gstack --skill retro-legotec73
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/legotec73/gstack/tree/main/retro
Command: npx skills add https://github.com/legotec73/gstack --skill retro-legotec73

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives can be time-consuming and opaque. This skill provides a structured, data-driven approach by analyzing commit history, PR activity, and code quality to surface praise and growth areas with persistent history and trend tracking.

Core Features & Use Cases

  • Analyze commit history, PR cadence, and quality signals to identify patterns and growth opportunities.
  • Break down contributions per person with praise and growth areas for individual coaching.
  • Enable both weekly sprint retrospectives and cross-project global retros by comparing windows and showing team-wide trends.

Quick Start

Run /retro to generate the weekly retrospective for the current project.

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 engineering retrospective from commit history?

To generate a data-driven engineering retrospective from commit history, you can run a command to analyze repository history, PR cadence, and code quality signals. This produces structured outputs to guide sprint planning and team coaching.

What is the best way to analyze team engineering metrics for weekly sprint reviews?

The best way to analyze team engineering metrics for weekly sprint reviews is by inspecting repository history and PR cadence to surface praise and growth areas. This data-driven approach replaces opaque retrospectives with per-person contribution insights.

Can I compare engineering activity and trends across multiple projects?

Yes, you can compare engineering activity and trends across multiple projects. The analysis enables cross-project global retros by comparing windows and showing team-wide trends to guide process changes.

Does generating a code history retrospective require persistent repository data?

Generating a code history retrospective does require persistent repository data. The analysis relies on persistent history to accurately track trend-based insights and deliver structured outputs for team coaching.

How do I identify individual growth areas and coaching opportunities from PR activity?

To identify individual growth areas and coaching opportunities from PR activity, the retrospective breaks down contributions per person. It analyzes quality signals to surface specific praise and targeted growth opportunities.

What limitations exist when tracking team growth metrics from code history?

A key limitation when tracking team growth metrics from code history is the reliance on persistent history. Without continuous repository data and consistent PR cadence, trend-based insights and cross-project comparisons may be incomplete.