retro

Analyze weekly commit history and code quality trends for engineering retrospectives.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill retro-ulanxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Ulanxx/mzstack/tree/main/retro
Command: npx skills add https://github.com/Ulanxx/mzstack --skill retro-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are hard to generate consistently, and teams struggle to derive actionable insights from commit history and code quality trends.

Core Features & Use Cases

  • Analyzes commit history, work patterns, and code quality metrics with persistent history.
  • Breaks down per-person contributions with praise and growth areas to help teams improve.
  • Proactively suggests focus areas at the end of a work week or sprint across projects.
  • Supports multi-project retros across all Claude-based coding tools for broader visibility.

Quick Start

Run /retro to generate a weekly retrospective for the last 7 days.

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 software engineering retrospective from git commit history?

Generate a weekly software engineering retrospective by analyzing git commit history to reveal contribution patterns, code quality trends, and process bottlenecks. Run /retro to automatically gather per-branch commits and per-author stats for the last 7 days.

Can I analyze team performance and code quality trends across multiple repositories?

You can analyze team performance and code quality trends across multiple repositories. The skill supports multi-project retros across all Claude-based coding tools, providing broader visibility into how the code evolved and where the team can improve.

What is the best way to break down per-author contributions for a sprint review?

The best way to break down per-author contributions for a sprint review is to analyze work patterns and code quality metrics with persistent history. This identifies who contributed what and highlights praise and growth areas to help teams improve.

Does the retrospective analysis work for single-repo and multi-repo contexts?

The retrospective analysis works for both single-repo and multi-repo contexts. It gathers per-branch commits and historical trends to inform leadership and engineers during sprint reviews regardless of your project scope.

How do I proactively identify process bottlenecks at the end of a work week?

Proactively identify process bottlenecks at the end of a work week by analyzing weekly software engineering activity. The skill suggests focus areas and reveals contribution patterns to help teams improve their workflow.

What kind of git statistics do I need to track code evolution trends over time?

To track code evolution trends over time, you need per-branch commits, per-author stats, and persistent historical data. The skill analyzes these git metrics to reveal how the code evolved and identify areas for team improvement.