retro

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

Updated Apr 24, 2026

Search Tags:#metrics #engineering #growth #git-history #retro #team-feedback

Ready to run

npx skills add https://github.com/MissTully/Gstack --skill retro-misstully

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/MissTully/Gstack/tree/main/retro
Command: npx skills add https://github.com/MissTully/Gstack --skill retro-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective that analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

Core Features & Use Cases

Analyzes commit history, work patterns, and code quality metrics with a persistent history.
Produces per-person contributions with praise and growth areas, helping teams identify improvement areas.
Proactively suggests action items at the end of a work week or sprint to close feedback loops.

Quick Start

Ask Claude to run a weekly retro on the current sprint to generate a team retrospective and growth plan.

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

To generate an engineering retrospective from git history, the Skill analyzes commit logs, work patterns, and code quality metrics to produce team-wide summaries and per-person growth notes for sprint reviews.

What metrics are analyzed in a team-wide engineering retro?▼

A team-wide engineering retro analyzes commit history, work patterns, and code quality metrics. It breaks down per-person contributions, highlighting praise and growth areas to identify team improvement areas.

How do I run a weekly retro on a current sprint?▼

Run a weekly retro by asking Claude to analyze the current sprint. The Skill requires access to a project's git history, a persistent history store, and the gstack runtime to produce actionable retro guidance.

Do I need a persistent history store for sprint-end reviews?▼

Yes, a persistent history store is required for sprint-end reviews. It enables trend tracking across weekly retros, allowing the Skill to compare past and current code quality metrics to generate actionable growth plans.

Can I automate engineering retros with action items and feedback loops?▼

Yes, you can automate engineering retros to close feedback loops. The Skill proactively suggests action items at the end of a work week or sprint, applying team-aware analysis to generate per-person growth notes.

Does the retro Skill work without gstack runtime?▼

No, the retro Skill requires the gstack runtime to function. Alongside gstack, it needs access to a project's git history and a persistent history store to process work patterns and generate retrospective guidance.