retro

Generate weekly engineering retrospectives from git history with per-person praise and growth opportunities.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives surface team-pattern insights from code activity, helping leaders and engineers understand where value is created and where growth is needed.

Core Features & Use Cases

  • Analyzes commit history, per-author contributions, and code quality signals to produce a structured weekly retrospective.
  • Provides persistent history and trend tracking to compare weeks and surface growth opportunities.
  • Delivers a narrative and metrics suitable for CTO-level review and team alignment.

Quick Start

Generate a weekly engineering retrospective 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 a weekly engineering retrospective from git history?

A git history retrospective analyzes commit data, test coverage, and PR sizes to produce a comprehensive weekly narrative with per-person praise and growth opportunities. It covers session patterns and file hotspots for CTO-level review.

What metrics are included in a git-based team retrospective?

Weekly retrospective metrics cover per-author commits, insertions, deletions, test coverage, and PR sizes. It also tracks file hotspots and session patterns, saving the history for trend analysis and week-to-week comparisons.

Can I track engineering team growth opportunities using commit analytics?

Yes, you can track growth opportunities by analyzing per-author contributions and code quality signals over time. The retrospective saves this history, allowing you to compare weeks and surface specific growth opportunities for your engineering team.

Does the weekly retrospective analysis work for CTO-level engineering reviews?

Yes, the weekly retrospective delivers a narrative and structured metrics suitable for CTO-level review. It analyzes git history to surface team-pattern insights, helping leaders understand where value is created and where growth is needed.

How do I compare engineering metrics across different weeks for my team?

You can compare engineering metrics across weeks using the retrospective's persistent history feature. It saves your weekly git analytics, enabling trend analysis and direct comparisons of per-person contributions and file hotspots over time.