retro

Analyze commit history and code quality metrics to generate weekly retrospectives.

Updated Mar 28, 2026

Search Tags:#retrospective #engineering #code-quality #sprint #retro #team-analysis

Ready to run

npx skills add https://github.com/steadyfall/fspeek --skill retro-steadyfall

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives provide a structured way to analyze commit history, work patterns, and code quality metrics with persistent history and trend tracking, enabling teams to learn and improve over time.

Core Features & Use Cases

Analyzes commit history, work patterns, and code quality metrics with a persistent history and trend tracking to surface patterns over time.
Breaks down per-person contributions with praise and growth areas, enabling constructive, team-led improvement conversations.
Provides a ready-to-review narrative for sprint retrospectives and project milestones.

Quick Start

Ask Claude to generate a weekly retro for this sprint by analyzing the latest commits, work patterns, and code quality metrics.

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

Generate an engineering retrospective from commit history by analyzing recent commits, work patterns, and code quality metrics to produce a narrative breakdown of per-person contributions with praise and growth areas.

What is a sprint retrospective and how does code quality tracking work?▼

A sprint retrospective analyzes team work patterns and code quality metrics to surface patterns over time, breaking down per-person contributions with praise and growth areas to enable constructive improvement conversations.

Can I track per-person contributions and growth areas for project milestones?▼

Yes, you can track per-person contributions for project milestones by analyzing commit history and work patterns, which breaks down individual metrics into praise and growth areas to enable constructive team-led improvement conversations.

Does this retrospective approach work for weekly sprints and milestone reviews?▼

Yes, this retrospective approach works for weekly sprints and milestone reviews by analyzing commit history and code quality metrics to produce a ready-to-review narrative with persistent history and trend tracking.

What is the best way to analyze code quality metrics for team improvement?▼

The best way to analyze code quality metrics for team improvement is to generate a repeatable weekly retrospective that tracks work patterns and commit history over time, surfacing actionable insights and per-person growth areas.

Why should I use persistent history and trend tracking for sprint retrospectives?▼

Use persistent history and trend tracking for sprint retrospectives to surface patterns over time from commit history and work patterns, enabling teams to learn and improve with actionable insights for constructive conversations.