retro

Analyze commit history and code-quality metrics to generate weekly engineering retrospectives.

Updated May 11, 2026

Search Tags:#git #retrospective #engineering #code-quality #sprint #team-growth

Ready to run

npx skills add https://github.com/wodeh/gstack-kimi --skill retro-wodeh

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives for engineering teams can be tedious to orchestrate and hard to standardize. This skill automatically analyzes commit history, work patterns, and code quality metrics to surface a consistent, team-aware retrospective with praise and growth opportunities.

Core Features & Use Cases

Analyzes historical activity to show per-person contributions and trends over time.
Produces actionable insights for sprint planning, process improvements, and learning goals.
Works across weekly cycles and ad-hoc project reviews, with persistent context across weeks.

Quick Start

Ask gstack to run "weekly retro" to generate the latest team retrospective and a 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 a weekly retrospective for my engineering team?▼

To generate a weekly retrospective, the skill analyzes engineering activity like commit history and work patterns to produce per-person contributions and growth signals. It surfaces a consistent, team-aware retrospective with praise and growth opportunities.

What is the best way to track sprint contributions and code quality trends?▼

Tracking sprint contributions and code quality trends is achieved by applying persistent history across weekly cycles. It aggregates commit data and code-quality metrics, generating actionable insights for sprint planning and learning goals.

How does analyzing git commit history improve team growth?▼

Analyzing git commit history improves team growth by identifying work patterns and code-quality metrics over time. It generates proactive growth suggestions and learning goals based on aggregated per-person contributions.

Can I use this for ad-hoc project reviews instead of weekly sprint cycles?▼

Yes, you can use it for ad-hoc project reviews as well as weekly sprint cycles. It applies release planning and project boundary rules to generate historical activity analysis while respecting privacy.

Does the retrospective analysis respect project boundaries and privacy?▼

Yes, the retrospective analysis respects project boundaries and privacy. It aggregates engineering activity within defined limits to produce team-aware insights without exposing sensitive individual data.