retro

Analyze git commit history and code quality metrics for weekly engineering retrospectives.

Updated Mar 30, 2026

Search Tags:#code quality #code review #engineering #commit history #retro

Ready to run

npx skills add https://github.com/joeylife94/gstack-2026-03 --skill retro-joeylife94

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you perform a comprehensive weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics. It provides a detailed breakdown of contributions and areas for improvement.

Core Features & Use Cases

Commit History Analysis: Reviews all commits in a specified time frame, including authorship, file changes, andLOC additions/deletions.
Work Pattern Insights: Identifies common files modified, commit frequency, and PRs merged.
Code Quality Metrics: Evaluates the health of tests and the project's TODO list.
Team Awareness: Tracks individual contributions and highlights areas for growth.

Quick Start

Run the /retro command to start a retrospective analysis 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 an engineering retrospective from git commit history?▼

To generate an engineering retrospective from git commit history, run the /retro command to analyze the last 7 days of contributions, work patterns, and code quality metrics. The Skill requires access to read your repository history and configuration.

What code quality metrics are included in a git repository retrospective?▼

A git repository retrospective includes code quality metrics such as lines of code added or deleted, common files modified, commit frequency, merged pull requests, project TODO list status, and the health of your tests.

Can I track individual and team contributions in a weekly code review retrospective?▼

Yes, you can track both individual and team contributions in a weekly code review retrospective. The Skill handles individual authorship tracking and highlights team areas for growth based on commit history and work patterns.

Do I need special permissions to analyze commit history for a project management retrospective?▼

Yes, you need permission to read git repository history and configuration files to analyze commit history for a project management retrospective. This access allows the Skill to review authorship, file changes, and code quality metrics.

What is the best way to analyze work patterns and commit frequency for engineering teams?▼

The best way to analyze work patterns and commit frequency is to use automated retrospective tools that parse git commit history, identify commonly modified files, and evaluate testing health to highlight areas for improvement.