skills.rest
JeremiahEllington
JeremiahEllingtonCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Apr 6, 2026
Search Tags:#git#retrospective#code-quality#commit-history#retro#team-growth
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill retro-jeremiahellington
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill retro-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking to deliver a team-wide retrospective with per-person praise and growth opportunities.

Core Features & Use Cases

  • Team-wide analysis of contributions and velocity
  • Persistent history with trend tracking over weeks
  • Per-person praise and actionable growth recommendations
  • Proactive suggestions at end of sprint or week

Quick Start

Run /retro after your sprint to generate a team retrospective with per-person insights.

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

To generate an engineering retrospective from git commit history, run a retrospective command after your sprint. It analyzes commit history, work patterns, and code quality metrics to deliver a team-wide retrospective with per-person praise and growth recommendations.

What is a team-aware code quality retrospective?▼

A team-aware code quality retrospective analyzes commit history and contribution metrics to generate trend-aware summaries. It provides per-person praise and actionable growth opportunities, tracking persistent history over weeks to identify team-wide velocity and work pattern trends.

Can I track engineering team growth trends over multiple weeks?▼

Yes, you can track engineering team growth trends over multiple weeks using persistent history tracking. The retrospective tool stores historical data to generate trend-aware summaries, allowing you to compare contribution metrics and code quality across previous sprints.

Does the retrospective provide per-person feedback for team members?▼

Yes, the retrospective provides per-person feedback for team members by analyzing individual commit history and work patterns. It generates tailored praise for contributions and actionable growth recommendations to support continuous team development.

What's the best way to analyze what we shipped during a sprint?▼

The best way to analyze what you shipped during a sprint is to run a weekly retro command. It evaluates your commit history and code quality metrics to produce a comprehensive summary of shipped work and team velocity.

Do I need any external dependencies to run a weekly retrospective?▼

No external dependencies are required to run a weekly retrospective. The tool operates independently using your existing git data and contribution metrics to analyze work patterns and generate trend-aware summaries.

Related Skills

Explore More Software Engineering Skills→
ByronWilliamsCPAByronWilliamsCPA

retro

Computes git commit analytics for development retrospective reports.

Official
Intermediate
mgher668mgher668

retro

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

Community
Advanced
makyua-sanmakyua-san

retro

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

Community
Advanced
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate