skills.rest
alexandervashurin
alexandervashurinCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyzes commit history and code quality metrics to generate team-aware retrospective reports with trend insights.

1|Updated Feb 25, 2026
Search Tags:#git#engineering#growth#code-quality#retro#team-feedback
One-click install
npx skills add https://github.com/alexandervashurin/semaphore --skill retro-alexandervashurin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/alexandervashurin/semaphore/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/alexandervashurin/semaphore --skill retro-alexandervashurin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives often miss persistent history and per-person growth opportunities. This skill automates a team-aware retrospective by analyzing commit history, work patterns, and code quality metrics, producing praise and growth recommendations for each contributor and maintaining a long-term history.

Core Features & Use Cases

  • Analyzes per-person contributions across a defined time window and surfaces growth opportunities.
  • Generates team-wide narratives plus individualized praise and actionable suggestions.
  • Keeps a persistent history and supports windowed comparisons to track trends over time.

Quick Start

Invoke the retro with a command like /retro [window] to generate a weekly engineering retrospective for the chosen time range.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate an engineering retrospective using git commit history?▼

Generate per-person growth opportunities by analyzing individual commit history and work patterns to produce tailored praise and actionable recommendations. This automated analysis tracks contributions and identifies specific areas for individual engineering improvement.

Can I compare engineering code quality metrics across different time windows?▼

Compare code quality metrics across different time windows using 24h, 7d, 14d, and 30d ranges. This persistent history feature tracks long-term trends and allows windowed comparisons to monitor team growth over time.

What is the best way to run a team-aware engineering retro?▼

Run a team-aware engineering retro by analyzing commit history and code quality metrics to generate persistent, per-person insights. This approach maintains long-term history while providing individualized feedback and team-wide narratives for the selected timeframe.

Does the engineering retro analysis require any external dependencies?▼

The engineering retro analysis requires no external dependencies to function. It operates independently to analyze commit history and work patterns, producing team-aware retrospectives with per-person praise and growth recommendations directly.

Related Skills

Explore More Software Engineering Skills→
jovermierjovermier
1

git-history-analyzer

Analyze repository commit history to trace code evolution and ownership.

Community
Basic
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced
garrytangarrytan
127.1k

gstack-openclaw-retro

Generate engineering retrospective reports from git commit history and code quality metrics.

Community
Advanced
BradliebsBradliebs

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced