retro

Aggregate git history and code-quality signals into weekly retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros analyze commit history, work patterns, and code-quality metrics to surface team-aware praise and growth opportunities, helping leaders and engineers improve over time.

Core Features & Use Cases

  • Analyzes commit history, work patterns, and quality metrics with persistent history and trend tracking.
  • Breaks down per-person contributions with praise and growth areas.
  • Provides actionable insights for sprint planning, process improvements, and skill development.

Quick Start

Type /retro to generate a weekly engineering retrospective for the current repository.

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?

Generate a weekly engineering retrospective by running /retro, which aggregates git history, per-author activity, hotspots, and code-quality signals to produce team-aware insights for the current repository.

Can I analyze git contributions for my whole team over a 30 day period?

Yes, you can analyze team git contributions over a 30 day period by passing time-window arguments, breaking down per-person contributions with specific praise and targeted growth areas.

What git metrics are needed to identify engineering bottlenecks and team dynamics?

Identifying bottlenecks requires git metrics like commit history, work patterns, and code-quality signals, which are aggregated to surface team dynamics and track improvements over time.

Does the weekly retro analysis support cross-project retrospectives?

Yes, weekly retro analysis supports a global mode that aggregates git history across projects, enabling cross-project retrospectives for senior engineers and leaders tracking broader engineering trends.

How do code-quality signals from git history improve sprint planning?

Code-quality signals from git history improve sprint planning by providing actionable insights for process improvements and skill development, surfacing team-aware growth opportunities based on commit patterns.