retro

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

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/filipnyquist/caidos --skill retro-filipnyquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/filipnyquist/caidos/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/filipnyquist/caidos --skill retro-filipnyquist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are laborious to compile, especially across many contributors and long commit histories. This Skill automates analysis of commit history, team patterns, and code quality metrics to produce a structured, actionable retrospective.

Core Features & Use Cases

  • Per-person contributions with praise and growth opportunities.
  • Persistent history and trend tracking across sprints.
  • Team-aware narratives that highlight momentum and areas for improvement.

Quick Start

Ask Claude Code to run /retro to generate the latest weekly engineering retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from git history?

You can automate weekly engineering retrospectives by analyzing commit history, work patterns, and code quality metrics to produce actionable team insights. This Skill extracts Git data to generate per-author contribution breakdowns and concise narratives.

What is a git commit history analysis for team reporting?

Git commit history analysis for team reporting extracts per-author contributions and code quality metrics to track team momentum. It identifies persistent trends and growth opportunities across engineering sprints.

How do I generate per-person engineering metrics and insights from git?

To generate per-person engineering metrics, extract per-author breakdowns from commit data to highlight individual praise and growth opportunities. The analysis identifies specific work patterns and code quality trends for each team member.

Can I track persistent sprint history and trends using git analytics?

You can track persistent sprint history and trends using git analytics by retaining per-author contribution data across multiple retrospectives. This allows you to monitor team momentum and identify long-term growth opportunities.

Does this retrospective tool work without external dependencies?

This retrospective tool works without external dependencies because it operates entirely within Claude Code. You simply run the command to generate the weekly engineering report from your local Git data.