retro

Analyze weekly git data to compute per-author metrics and session patterns.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/GS-Personal/gstack --skill retro-gs-personal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/GS-Personal/gstack/tree/main/retro
Command: npx skills add https://github.com/GS-Personal/gstack --skill retro-gs-personal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives enable engineering teams to turn code activity into actionable insights, surfacing patterns, celebrating wins, and identifying improvement opportunities from a data-rich perspective.

Core Features & Use Cases

  • Per-week contributor leaderboard highlighting who moved the codebase.
  • Time-window metrics for commits, LOC, test activity, PR velocity, and session patterns.
  • Narrative-ready summaries including a personal "Your Week" view and a "Team Wins" highlight.

Quick Start

Run a retrospective for the last 7 days and review the resulting narrative for actionable takeaways.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate engineering metrics from git history for a team retro?

Generate engineering metrics for a team retro by analyzing a week of git data from origin/main. The tool computes per-author commits, insertions, deletions, and PR velocity to frame a team-level improvement narrative.

Can I track individual contributor code activity and PR velocity over a specific time window?

Track individual contributor code activity and PR velocity by computing time-window metrics from git history. The analysis highlights per-week contributor leaderboards to show exactly who moved the codebase.

How do I turn git commit data into a narrative summary for sprint retrospectives?

Turn git commit data into a narrative summary by structuring per-author metrics, hotspots, and session patterns for ingestion into retro tools. It produces a personal view and a team wins highlight.

What git data is needed to compute test signals and session patterns for an engineering retrospective?

Git data needed to compute test signals and session patterns includes commits, insertions, deletions, and PR activity from origin/main. The analysis evaluates these inputs to surface time-based trends.

Does this approach to weekly retrospectives work without integrating external CI/CD platforms?

This approach to weekly retrospectives works without external CI/CD platforms by analyzing git data directly from origin/main. It computes test signals and PR activity metrics solely from repository history.

What is the best way to identify code hotspots and improvement opportunities from recent commits?

The best way to identify code hotspots and improvement opportunities from recent commits is to analyze a week's worth of git data. This surfaces actionable insights and session patterns for team-level improvement.