retro

Generate weekly engineering retrospectives from git logs, tests, and PR activity.

1|Updated Dec 23, 2025

Search Tags:#metrics #engineering #code-quality #git-history #retro #team-analysis

Ready to run

npx skills add https://github.com/rkumar261/studio-cast --skill retro-rkumar261

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that translate raw git history, commit activity, and code signals into a clear, actionable narrative for teams. It highlights praise, growth opportunities, and patterns that influence future delivery.

Core Features & Use Cases

Per-person praise and growth opportunities based on commit activity, LOC, tests, and hotspot analysis.
Time-windowed retrospectives with a default 7 days and options for 24h, 14d, 30d, and compare mode to assess changes over time.
Rich signals coverage including PR counts, hotspot files, test health signals, backlog status when TODOS.md exists, and team-pace patterns to guide focus.

Quick Start

Run the retro skill with the desired window to generate a comprehensive weekly engineering retrospective summary.

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

To generate a weekly engineering retrospective, you can analyze commit histories, test stats, and PR activity over a default 7-day window to produce a structured narrative with per-author praise and growth opportunities.

Can I analyze code quality metrics for individual team members based on commits?▼

Yes, you can analyze code quality metrics for individual team members by evaluating commit activity, lines of code, test health signals, and hotspot files to generate targeted per-person praise and growth opportunities.

What is the best way to compare engineering team activity across different time periods?▼

The best way to compare engineering team activity across time periods is using a compare mode alongside configurable time windows like 24h, 14d, or 30d to assess changes in commit patterns and hotspot analysis over time.

Does the retrospective analysis work with backlog files like TODOS.md?▼

Yes, the retrospective analysis works with backlog files by automatically detecting and incorporating backlog signals from TODOS.md when available, integrating this status into the final team-pace retrospective narrative.

How to identify code hotspot files affecting team delivery and focus areas?▼

To identify code hotspot files affecting team delivery, you analyze git logs and test health signals to pinpoint highly active files, generating actionable focus area signals and historical context for the engineering team.