retro

Generates engineering retrospectives from git commit history and timeline events.

Updated Jun 5, 2026

Search Tags:#git #analytics #productivity #retrospective #engineering #team-management

Ready to run

npx skills add https://github.com/smarmen86/claude-code-kit --skill retro-smarmen86

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/retro
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill retro-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of manually tracking team progress, shipping velocity, and engineering learnings, which often leads to fragmented project history and missed opportunities for growth.

Core Features & Use Cases

Automated Retrospective Generation: Analyzes commit history, work patterns, and timeline events to generate a comprehensive weekly retrospective.
Team-Aware Insights: Breaks down contributions by individual, highlighting both praise and specific areas for professional growth.
Use Case: At the end of a sprint, use this skill to generate a summary of what the team shipped, identify recurring technical hurdles, and surface key learnings from the past week.

Quick Start

Invoke the retro skill to generate an engineering retrospective based on the recent commit history and project timeline.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate engineering retrospectives from git commit history?▼

Automating engineering retrospectives from git commit history involves analyzing project timeline events and work patterns to synthesize team contributions. This skill generates structured performance documentation by parsing local filesystem logs and commit data to surface technical hurdles and key learnings.

What is the best way to track team shipping velocity for a sprint?▼

Tracking team shipping velocity for a sprint is best handled by generating a comprehensive weekly retrospective that analyzes work patterns and commit history. This approach highlights individual contributions while identifying recurring technical hurdles and specific areas for professional growth.

Does generating automated engineering retrospectives require gstack-configured analytics tools?▼

Generating automated engineering retrospectives does require gstack-configured analytics tools along with access to local filesystem logs and git history. These dependencies are necessary to synthesize project timeline events and accurately track continuous improvement documentation for team-based software development.

Can I analyze individual developer contributions within a team-based software development workflow?▼

Analyzing individual developer contributions within a team-based software development workflow is fully supported. The skill processes commit history to generate team-aware insights, breaking down contributions by individual to highlight both praise and specific areas for professional growth.

When should I use an automated retrospective instead of manual project tracking?▼

Using an automated retrospective instead of manual project tracking is ideal when team progress becomes fragmented and engineering learnings are missed. It solves the challenge of manually tracking shipping velocity by automatically synthesizing commit history and timeline events into structured performance documentation.