retro

Analyze git history and code metrics to generate weekly engineering retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that automatically analyze commit history, work patterns, and code quality metrics to produce team-aware insights and growth opportunities.

Core Features & Use Cases

  • Team-wide analysis of contributions with per-person praise and growth areas.
  • Persistent history of retros and a clear narrative to guide improvements.
  • Focus on hotspots, PR sizes, and test signals to drive shipping decisions.

Quick Start

Ask Claude to run /retro to generate a weekly engineering retrospective for the last 7 days.

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 git history?

Generate a weekly engineering retrospective by running /retro, which reads git commit history to compute work patterns, PR sizes, and code quality metrics for the last 7 days. It outputs a narrative with team insights and per-person feedback.

Can I analyze team engineering metrics like PR sizes and focus patterns from git commits?

Analyze team engineering metrics by applying the retro Skill to your git commits. It computes focus patterns, PR sizes, and code hotspots, presenting the results in a structured team leaderboard with actionable growth opportunities.

What engineering leadership metrics are included in a team retrospective?

Engineering leadership metrics in a team retrospective include per-person praise, growth areas, focus patterns, PR sizes, test signals, and code hotspots. These metrics are aggregated into a narrative that explains insights and recommends shipping decisions.

Does the weekly retrospective analysis work for individual contributors or just team-wide contexts?

Weekly retrospective analysis works for both team-wide and per-user contexts. It applies to a configurable weekly window, defaulting to 7 days, and generates per-person praise and growth opportunities alongside the team leaderboard.

How are code hotspots and test signals used to drive shipping decisions in a retrospective?

Code hotspots and test signals are aggregated from git history to highlight risk areas and quality trends. The retrospective narrative uses these signals to explain potential blockers and recommend targeted actions for shipping decisions.

Best way to track engineering team trends and work patterns over time?

Track engineering team trends by running weekly retrospectives that aggregate commit history and work patterns into persistent reports. This builds a history of retros that reveals focus patterns, PR size trends, and code hotspots to guide continuous improvement.