retro

Analyze commit history and code quality metrics into weekly engineering retrospectives.

Updated Mar 29, 2026

Search Tags:#git #engineering #growth #trend-analysis #retro #team-performance #praise

Ready to run

npx skills add https://github.com/zzxtbeta/design-handbook --skill retro-zzxtbeta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/zzxtbeta/design-handbook/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/zzxtbeta/design-handbook --skill retro-zzxtbeta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly distill a week's worth of engineering activity into a focused, team-aware retrospective that highlights contributions, pattern shifts, and growth opportunities.

Core Features & Use Cases

Per-person praise and growth areas derived from commit history and metrics.
Persistent history and trend tracking to monitor improvements across sprints.
Proactive prompts at week end to guide planning and next steps.

Quick Start

Type /retro to generate the weekly engineering retrospective for the current sprint.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a weekly engineering retrospective from git commit history?▼

To generate a weekly engineering retrospective, this Skill analyzes git commit history and work patterns to summarize per-person contributions, trends, and actionable growth areas. You simply type /retro to start the analysis.

What is the best way to analyze team performance trends across multiple sprints?▼

Analyzing team performance trends requires persistent history storage to track improvements across sprints. This Skill uses persistent trend tracking to monitor code quality metrics and per-person growth areas over time.

Can I use commit history to highlight per-person praise and growth areas for sprint reviews?▼

Yes, you can use commit history to highlight per-person praise and growth areas. The Skill derives these insights from commit history and code quality metrics, making it useful for sprint reviews and growth planning.

Do I need persistent history storage to track engineering work patterns and improvements?▼

Yes, persistent history storage is required. The Skill needs access to git history over a defined window and persistent storage to track work patterns, monitor improvements, and provide trend analysis across sprints.

How does a weekly retro help with proactive sprint planning and growth analysis?▼

A weekly retro helps with sprint planning by providing proactive prompts at week end to guide next steps. It analyzes engineering activity to output actionable insights, praise, and growth areas for the team.

What engineering activity metrics are needed for a focused team-aware retrospective?▼

A focused team-aware retrospective requires git commit history, work patterns, and code quality metrics over a defined window. The Skill distills these engineering activity metrics into per-person contributions and trend shifts.