skills.rest
TobiasPerry
TobiasPerryCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze commit history and team metrics to generate structured weekly engineering retrospectives.

Updated Mar 27, 2026
Search Tags:#commit-history#retro#leaderboard#git-analytics#team-metrics#engineering-retrospective
One-click install
npx skills add https://github.com/TobiasPerry/aws-hackathon --skill retro-tobiasperry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/TobiasPerry/aws-hackathon/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/TobiasPerry/aws-hackathon --skill retro-tobiasperry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes commit history, team participation, and code-quality signals to produce a structured weekly engineering retrospective that surfaces praise, growth opportunities, and historical trends.

Core Features & Use Cases

  • Per-person contributions with praise and growth areas.
  • Global and project-specific retrospectives with trend analysis across time windows.
  • Comprehensive metrics such as commits, LOC, hotspots, test health, and a per-author leaderboard.
  • Actionable summaries that guide team improvements and planning.

Quick Start

Run /retro to generate a weekly retro for the last 7 days in the current repository.

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

A weekly engineering retrospective analyzes commit history and code-quality signals to surface team contributions, hotspots, and historical trends. It computes metrics such as per-author leaderboards, focus scores, and backlog health to guide continuous improvement.

Can I run an engineering retrospective across multiple repositories or custom time windows?▼

Yes, engineering retrospectives support cross-project contexts and custom time windows beyond the default last 7 days. You can generate global comparisons and trend analysis across multiple repositories to evaluate team metrics over specific retrospective periods.

What team metrics are included in a git analytics retrospective?▼

A git analytics retrospective includes per-author contributions, commit counts, lines of code, focus scores, ship-of-the-week, hotspot analysis, and backlog health. These metrics populate an intuitive leaderboard to highlight individual and team activity for the period.

Does the engineering retrospective require any external dependencies to analyze code-quality signals?▼

No external dependencies are required to analyze code-quality signals for the engineering retrospective. The skill operates independently to evaluate commit history, team participation, and test health directly from the repository context without additional setup.

How do I identify growth areas and praise opportunities from developer contribution metrics?▼

To identify growth areas and praise opportunities, the retrospective evaluates per-person contributions against team activity and code-quality signals. It surfaces actionable summaries that highlight specific praise and targeted growth areas for each developer automatically.

Related Skills

Explore More Software Engineering Skills→
giljaegiljae
1

gstack-retro

Analyze git logs and pull requests to generate engineering retrospective reports.

Community
Advanced
DonchitosDonchitos
23.7k

retrospective

Generate sprint retrospective reports from git logs and project plans.

Community
Advanced
I-OnlabsI-Onlabs
3

code-auditor

Audit codebases across architecture, quality, security, and performance to produce prioritized health reports.

Community
Advanced
CarbeneAICarbeneAI
9

retro

Generate weekly engineering retrospectives from git logs and analytics files.

Community
Advanced