retro

Analyze commit history and contribution patterns to generate weekly engineering retrospective reports.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill retro-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill retro-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are often manual, time-consuming, and inconsistent. This Skill automates the collection and analysis of commit history, contribution patterns, and quality signals to generate actionable team insights.

Core Features & Use Cases

  • Team-aware retrospectives that identify praise and growth opportunities per contributor.
  • Windowed analysis of commits, insertions, deletions, hotspots, and focus areas across repositories.
  • Quick-start workflow to produce a structured retro report for a chosen time window.

Quick Start

Run /retro to generate the latest weekly retrospective 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 automate weekly engineering retrospectives using commit history?

You can generate an automated weekly retrospective by running the /retro command, which analyzes commit history, contribution patterns, and quality metrics over a default 7-day window to produce a structured report.

What is cross-repo focus analysis and when do I need it for team metrics?

Cross-repo focus analysis evaluates commit hotspots and contribution patterns across multiple repositories to identify team focus areas, needed when your engineering team works across several repositories and requires consistent windowed comparisons.

Can I generate per-author praise and growth suggestions from contribution patterns?

Yes, generating per-author praise and growth suggestions from contribution patterns is supported. The retrospective synthesizes individual commit data to highlight specific achievements and areas for improvement for each contributor.

Does the retrospective analysis work with windowed comparisons for different time frames?

Yes, the retrospective analysis supports windowed comparisons. While the quick-start workflow uses a default 7-day window, you can specify a chosen time window to compare metrics like insertions, deletions, and hotspots consistently.

What's the best way to export engineering team metrics for consistent improvement?

The best way to export engineering team metrics is to use the Skill's end-to-end data collection and metrics synthesis, which produces an export-ready summary of team insights and quality signals for consistent improvement tracking.

Do I need external dependencies to run commit history analysis for retrospectives?

No external dependencies are required to run commit history analysis. The Skill implements end-to-end steps for data collection, metrics synthesis, and reporting internally without relying on additional components.