skills.rest
primovera12
primovera12COMMUNITY
Explore all skills by this author →
GitHub

retro

Aggregate Git commit history, work logs, and sprint state into retrospective summaries.

Updated Aug 23, 2026
Search Tags:#git#analysis#velocity#sprint#worklog#retro
One-click install
npx skills add https://github.com/primovera12/Master-Kit --skill retro-primovera12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/primovera12/Master-Kit/tree/main/Master-Starter-Kit/tools/skills/retro
Command: npx skills add https://github.com/primovera12/Master-Kit --skill retro-primovera12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams quickly generate a cohesive retrospective by analyzing commit history, work logs, and sprint state over a selected date range, saving time and surfacing actionable insights.

Core Features & Use Cases

  • Velocity & commit analysis: tracks throughput, burn, and patterns across sprint history.
  • Work-log & session cadence: detects activity windows and focus sessions.
  • Trend insights: compares periods to highlight momentum changes.
  • Use cases include post-sprint reviews, weekly progress checks, and identifying bottlenecks or quality signals.

Quick Start

Invoke /retro to generate a seven-day narrative retrospective from recent commits and work-log data.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a sprint retrospective from Git commit history and work logs?▼

Track sprint velocity by analyzing commit throughput and burn patterns across sprint history, detecting activity windows and focus sessions from work logs to highlight momentum changes.

Can I compare velocity trends between current and prior sprint periods?▼

Identify bottlenecks and quality signals by analyzing commit throughput, burn patterns, and work-log session cadence over a date range to surface activity windows and focus session trends.

Does sprint velocity analysis require access to Git history and work-log data sources?▼

Sprint velocity analysis requires access to Git history and work-log data sources to compute metrics, detect activity windows, and generate narrative summaries for the selected retrospective date range.

What is the best way to run a post-sprint review using commit and work-log analysis?▼

Run a post-sprint review by invoking a seven-day narrative retrospective from recent commits and work-log data, comparing prior period metrics to surface velocity trends and actionable insights.

Can I analyze work-log session cadence to detect focus periods across a sprint?▼

Analyze work-log session cadence to detect activity windows and focus sessions across a selected date range, surfacing throughput patterns and momentum changes for sprint retrospective insights.

Related Skills

Explore More Software Engineering Skills→
josephneumannjosephneumann
4

retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
HouseofmvpsHouseofmvps
115

retro

Analyze git repository history to generate structured sprint retrospective reports.

Community
Intermediate
solace-illsolace-ill

retrospective

Generate markdown retrospectives from sprint data and git history.

Community
Advanced