retro

Generate weekly engineering retrospectives from Git commit history and code metrics.

5|1|Updated Mar 15, 2026

Search Tags:#git #code analysis #productivity #retrospective #engineering metrics #team performance

Ready to run

npx skills add https://github.com/jianshuo/Cathier --skill retro-jianshuo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jianshuo/Cathier/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/jianshuo/Cathier --skill retro-jianshuo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive weekly engineering retrospectives, analyzing code contributions, identifying team patterns, and highlighting areas for improvement.

Core Features & Use Cases

Automated Data Collection: Gathers commit history, author data, and code metrics from Git.
Team & Individual Analysis: Provides insights into team-wide trends and individual contributions, including praise and growth opportunities.
Trend Tracking: Compares current data against historical retrospectives to show progress and regressions.
Use Case: Run /retro at the end of each week to get a detailed report on team velocity, code quality, and individual performance, enabling data-driven discussions and improvements.

Quick Start

Run the retro skill for the last 7 days of activity.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate engineering retrospectives using Git commit history?▼

You can automate engineering retrospectives by running the retro skill, which analyzes Git commit history, author contributions, and code quality metrics to generate detailed weekly reports. It tracks performance trends and identifies areas for team improvement.

What engineering metrics are tracked in automated weekly code retrospectives?▼

Automated weekly code retrospectives track team velocity, code quality, and individual performance patterns. The analysis compares current Git data against historical trends to highlight progress, regressions, and actionable feedback for continuous improvement.

Can I generate individual performance insights from Git author data?▼

Yes, you can generate individual performance insights from Git author data. The retrospective analysis evaluates author contributions to provide specific feedback, recognizing individual achievements and identifying growth opportunities within the team.

How do I compare current team performance against historical engineering trends?▼

You can compare current team performance against historical engineering trends by running the retrospective tool. It evaluates current Git metrics alongside historical retrospective data to show progress and regressions over time, enabling data-driven team discussions.

Do I need additional dependencies to analyze code quality metrics from Git?▼

No, you do not need additional dependencies to analyze code quality metrics from Git. The retrospective skill operates independently, utilizing built-in Git commands and data processing scripts to gather commit history and generate comprehensive reports.

What is the best way to track team velocity and code quality over time?▼

The best way to track team velocity and code quality over time is through automated weekly retrospectives. By consistently analyzing Git commit history and engineering metrics, the tool identifies performance patterns and provides actionable feedback for continuous improvement.