skills.rest
steffenpharai
steffenpharaiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze git history to generate team engineering retrospectives with structured metrics.

Updated Aug 27, 2026
Search Tags:#git#productivity#metrics#engineering#code-review#retro#team-analysis
One-click install
npx skills add https://github.com/steffenpharai/StartupFramework --skill retro-steffenpharai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/steffenpharai/StartupFramework/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/steffenpharai/StartupFramework --skill retro-steffenpharai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives with AI-assisted analysis of commit history, work patterns, and code quality metrics to surface per-person praise and growth opportunities. The retro helps teams reflect on contributions and identify improvement areas for upcoming cycles.

Core Features & Use Cases

  • Analyze commits, LOC, tests, hotspots, and contributor trends within a configurable time window.
  • Produce a team-wide narrative with per-person praise and growth opportunities, plus actionable focus areas and ship signals.
  • Support multiple windows (7d default, 24h, 14d, 30d) and compare mode; outputs structured metrics, leaderboards, and a narrative suitable for sharing with teams.

Quick Start

Run /retro in Cursor to generate the latest weekly retro for the default 7-day window.

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

To generate an engineering retrospective from git history, run the tool in Cursor to analyze commits, LOC, tests, and contributor trends, producing a narrative with per-author metrics for your specified time window.

What is a git-based team retrospective and what metrics does it include?▼

A git-based team retrospective analyzes commit history to summarize work patterns, outputting structured metrics including lines of code, test coverage, commit hotspots, and a per-author leaderboard with actionable growth opportunities.

Can I analyze git commits for a custom time window like 24 hours or 30 days?▼

Yes, you can analyze git commits for custom time windows. The tool supports configurable parameters including 24h, 14d, 30d, and compare modes, with a 7-day default window for standard weekly engineering reviews.

Does the engineering retrospective tool work for post-release reflections?▼

Yes, the engineering retrospective tool works for post-release reflections. It applies historical commit analysis to surface team-wide ship signals and contributor trends, making it suitable for onboarding and release reviews.

How do I get per-person praise and growth opportunities from code review data?▼

To get per-person praise and growth opportunities from code review data, the tool evaluates individual git contributions and commit patterns, generating a team-aware narrative that highlights specific achievements and improvement areas.

Related Skills

Explore More Software Engineering Skills→
flashpoint493flashpoint493
1

VibeCollab — Setup Instructions for AI Assistants

Install and configure VibeCollab with MCP Server support for AI-assisted workflows.

Community
Intermediate
BatsiraiBatsirai

retro

Analyze Git commit history and code quality metrics to generate team-aware retrospective narratives.

Community
Advanced
hetsheth-droidhetsheth-droid

retro

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

Community
Advanced
jewbetchajewbetcha
115

changelog-generator

Generate user-facing release notes from Git commit history.

Community
Basic