retro

Name: retro
Availability: InStock
Author: chriswestt

Generates weekly engineering retrospectives from commit history and code quality metrics.

Updated Apr 21, 2026

Search Tags:#retrospective #engineering #code-quality #commit-history #team-performance #growth-trends

Ready to run

npx skills add https://github.com/chriswestt/claude-skills --skill retro-chriswestt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

Core Features & Use Cases

Automatic weekly retrospectives: summarize what shipped, what patterns emerged, and where to improve.
Per-person insights: highlight individual contributions, collaboration patterns, and growth opportunities.
Persistent history & trends: maintain a running record and show improvement or regression over time.

Quick Start

Tell Claude to run a weekly retro for the current sprint and summarize the week's commits, patterns, and growth opportunities.

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

To generate a weekly engineering retrospective, the Skill analyzes commit history, work patterns, and code quality metrics to summarize what shipped and highlight growth areas. It requires access to repository data and team context to produce accurate, team-aware insights.

Can I track team performance and growth trends over multiple sprints?▼

Yes, you can track team performance and growth trends over multiple sprints using persistent history. The Skill maintains a running record of code quality metrics and per-person contributions to show improvement or regression over time.

What's the best way to analyze per-person code quality and work patterns?▼

The best way to analyze per-person code quality and work patterns is by breaking down individual contributions during a weekly review. The Skill highlights collaboration patterns, offering specific praise and identifying growth opportunities for each team member.

Do I need repository data and historical metrics to run a sprint retrospective?▼

Yes, you need repository data, historical metrics, and team context to run an accurate sprint retrospective. The Skill relies on this access to analyze commit history and generate team-aware insights for your weekly review.

What does an automated sprint retrospective include for engineering teams?▼

An automated sprint retrospective for engineering teams includes a summary of what shipped, what work patterns emerged, and where to improve. It breaks down per-person contributions with specific praise and actionable growth areas based on commit history.