retro

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

Updated Mar 28, 2026

Search Tags:#workflow #metrics #engineering #code-quality #retro #team-growth

Ready to run

npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill retro-zaeem-rafiq

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives analyze commit history, work patterns, and code quality metrics to surface team praise and growth opportunities with persistent history.

Core Features & Use Cases

Team-aware retrospectives with per-person contributions, praise, and growth areas.
Generates trend insights and growth plans across sprints and teams.
Use when asked for "weekly retro", "what did we ship", or "engineering retrospective" to guide improvements.

Quick Start

Ask Claude to run /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 commit history?▼

Generate an engineering retrospective by analyzing commit history, work patterns, and code quality metrics. This Skill computes per-author contributions and session patterns to surface team praise and growth opportunities.

Can I analyze individual contributor metrics during a weekly retrospective?▼

Yes, weekly retrospectives can analyze data across individual contributors or the entire team. It computes per-author metrics and session patterns to highlight specific praise and growth areas for each developer.

What code quality metrics are used to surface team growth opportunities?▼

Code quality metrics are analyzed alongside commit history and work patterns to identify growth opportunities. The system processes these metrics to generate trend insights and structured growth plans across sprints.

How do I run a weekly retro to see what my team shipped?▼

Run a weekly retro by asking Claude to execute the /retro command. It identifies and summarizes weekly engineering outputs by analyzing your commit history and generating a narrative snapshot for review.

Does the engineering retrospective work for analyzing multi-sprint trends?▼

Yes, retrospectives generate trend insights and growth plans across sprints and teams. The analysis maintains persistent history to track engineering work patterns and code quality improvements over time.