retro

Name: retro
Availability: InStock
Author: mgher

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

Updated Apr 13, 2026

Search Tags:#engineering #growth #code-quality #commit-history #retro #praise

Ready to run

npx skills add https://github.com/mgher668/surf-ai --skill retro-mgher668

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are hard to correlate with code history and team dynamics. This Skill automates the generation of a structured engineering retrospective by analyzing commit history, work patterns, and code quality metrics, delivering a clear, actionable narrative for the team.

Core Features & Use Cases

Team-aware analysis breaks down per-person contributions with praise and growth areas.
Trend tracking & persistence maintains a persistent history across weeks and sprints to show improvement.
Context-aware outputs supports prompts like "weekly retro" or "what did we ship" to surface relevant insights.

Quick Start

Ask me for a weekly retro with /retro and I will generate the report.

Frequently Asked Questions about retro

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

FAQPage Schema

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

Automating a weekly engineering retrospective analyzes commit history and code quality metrics to generate a structured report with per-person praise and growth areas. It correlates code history with team dynamics to produce an actionable narrative.

Can I track engineering growth and code quality trends across multiple sprints?▼

Tracking engineering growth across sprints requires persistent history to show improvement over time. This approach maintains trend tracking across weeks, delivering team-aware summaries that highlight continuous code quality and contribution patterns.

How does team-aware analysis break down individual engineering contributions?▼

Team-aware analysis breaks down per-person contributions by evaluating commit history and work patterns, then generating specific praise and targeted growth opportunities for each developer within the weekly retrospective.

Do I need any external dependencies to generate code quality retrospectives?▼

Generating code quality retrospectives requires no external dependencies. The process integrates directly with Claude workflows, using commit history and work pattern data to produce context-aware outputs for weekly sprints.

What is the best way to summarize what my team shipped this week?▼

The best way to summarize what your team shipped is by analyzing commit history and code quality metrics to generate a structured engineering retrospective. This delivers a clear, actionable narrative covering work patterns and team dynamics.

How do I generate a retro report for my project team?▼

Generating a retro report for project teams involves analyzing commit history and code quality metrics to produce a weekly engineering retrospective. The output provides team-wide insights with per-person praise and growth opportunities.