retro

Analyze commit history and work patterns to generate engineering retro summaries.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/greencm/gstuck --skill retro-greencm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/greencm/gstuck/tree/main/output/gstack/retro
Command: npx skills add https://github.com/greencm/gstuck --skill retro-greencm

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the engineering retro process by automating the analysis of commit history, work patterns, and code quality metrics, making it easier to review and discuss progress and learnings.

Core Features & Use Cases

  • Automated Analysis: Analyzes commit history, work patterns, and code quality.
  • Persistent History: Tracks and presents trends over time.
  • Team-Aware: Breaks down contributions by team members with praise and areas for growth.
  • Use Case: Use this Skill when conducting a weekly retro to quickly review past work, identify areas of improvement, and discuss learnings.

Quick Start

Run the retro skill to automatically generate a summary of the past week's engineering work.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate engineering retro analysis using commit history?

Automating engineering retro analysis involves parsing commit history and work patterns to generate insights into code quality and team contributions. This Skill reads project files and commit logs to summarize progress and learnings automatically.

What is the best way to analyze team contributions from commit logs?

Analyzing team contributions from commit logs requires breaking down commit history by author to identify individual work patterns. This process highlights areas for growth and praise, making weekly engineering retrospectives more data-driven.

Does this automated retro tool require access to project files?

Yes, automated retro analysis requires direct access to your project files and commit history. The tool uses Bash, Glob, and Read operations to evaluate code quality metrics and work patterns locally.

How do I run a weekly engineering retro to review code quality?

To run a weekly engineering retro, execute the Skill to automatically scan recent commit history and project files. It generates a summary of past work, identifies code quality trends, and surfaces learnings for team discussion.

Can I track engineering work patterns and learnings over time?

Yes, tracking engineering work patterns over time is supported through persistent history features. The analysis evaluates commit trends across intervals, allowing you to review progress and code quality improvements historically.