retro

Generate per-author Git retrospective reports with growth opportunities and metrics.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bananaduck1/storylab --skill retro-bananaduck1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/bananaduck1/storylab/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/bananaduck1/storylab --skill retro-bananaduck1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the generation of weekly engineering retrospectives by analyzing commit history, contributor activity, and code quality metrics, providing a clear narrative and actionable insights.

Core Features & Use Cases

  • Per-author retrospectives with growth opportunities and praise.
  • Repository-wide metrics including commits, insertions/deletions, PRs merged, test signals, and hotspots.
  • Leaderboard-style contributor view with actionable recommendations to improve processes and quality.

Quick Start

Type /retro to generate the latest weekly retrospective for the current repository window.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from Git history?

Automating weekly engineering retrospectives uses commit history, contributor activity, and code quality metrics to generate a structured summary with actionable growth opportunities. It parses project Git history to produce per-author insights.

Can I generate per-author code quality metrics from commit data?

Generating per-author code quality metrics from commit data parses diffs and test files to produce contributor-specific retrospectives. It includes metrics like commits, insertions, deletions, test health, and hotspots tailored to the current user.

How do I create a contributor leaderboard with actionable process recommendations?

Creating a contributor leaderboard with actionable recommendations analyzes repository-wide commit history and test signals. It outputs a leaderboard-style view with insights to improve engineering processes and code quality.

Does the retrospective analysis require access to diffs and test files?

Retrospective analysis requires access to commit data, diffs, test files, and optional telemetry data. It applies to the current repository window or a global cross-project view to output a structured summary suitable for review workflows.

What is the best way to analyze test health and hotspots across multiple repositories?

Analyzing test health and hotspots across multiple repositories uses a global cross-project view of Git history. It parses commit data and diffs to produce a concise retrospective with metrics highlighting areas needing attention.

Can I use this retrospective tool for individual growth opportunities and praise?

Using this retrospective tool for individual growth opportunities and praise analyzes per-author commit history and code quality metrics. It generates a concise narrative highlighting actionable growth areas and specific contributor praise.