retro

Analyze git history and team activity to generate weekly engineering retrospectives.

Updated Mar 29, 2026

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

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with a team-aware perspective, delivering praise and growth guidance.

Core Features & Use Cases

Provides per-person contribution breakdowns and actionable feedback.
Tracks history and trends across sprints to reveal patterns in work and quality.
Proactively surfaces focus areas at sprint end to guide planning and improvement.

Quick Start

Run /retro to generate the current week's engineering retrospective.

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 engineering retrospective from git history?▼

Generating a weekly engineering retrospective from git history involves analyzing recent commits and team activity to identify patterns across contributors, hotspots, and code quality signals. The tool outputs per-author praise and growth areas.

What metrics does an engineering retrospective track for team growth?▼

An engineering retrospective tracks code quality metrics, commit history, and work patterns to reveal trends across sprints. It provides per-person contribution breakdowns and actionable feedback to guide team growth and planning.

Can I run retrospectives for a single-team project over a specific week window?▼

Yes, you can run retrospectives for a single-team project over a specific week window. The analysis applies to single-team projects, processing local analytics and git data to produce concise, actionable feedback.

How do I get per-author praise and growth areas from recent commits?▼

To get per-author praise and growth areas from recent commits, run a weekly engineering retrospective. It identifies patterns in recent commits and team activity, delivering concise, actionable feedback for each contributor.

Is there a global retro mode for analyzing multiple contributors?▼

Yes, there is an optional global retro mode for analyzing multiple contributors. It identifies patterns in recent commits and team activity to produce an actionable weekly engineering retrospective across contributors.

When should I not use automated engineering retrospectives?▼

You should not use automated engineering retrospectives outside a single-team project context or a one-week window. The analysis is specifically scoped to recent commits and local analytics data over a weekly period.