retro

Collect and analyze Git history to generate a weekly retrospective markdown report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are essential for teams to reflect on past work, identify bottlenecks, and align on improvements, but manual aggregation from Git history is tedious and error-prone.

Core Features & Use Cases

  • Collect recent commits and file changes from the past week to form a cohesive narrative
  • Analyze hotspots, patterns, and evolution of features or fixes to surface actionable insights
  • Generate a concise, shareable weekly retrospective that can be used in team meetings and post-mortems

Quick Start

Run the retro workflow to collect the last week's commits and generate a summary.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a weekly retrospective from Git commit history?

You can automate a weekly retrospective by collecting recent Git commits and file changes to generate a concise markdown report. This workflow analyzes hotspots and patterns to surface actionable insights for team meetings.

What is the best way to analyze Git hotspots and commit patterns for a team review?

Analyzing Git hotspots involves reviewing commit history and file changes to identify evolution of features or fixes. This process surfaces actionable insights and patterns to form a cohesive narrative for team post-mortems.

Can I generate a markdown report of recent Git changes for sprint retrospectives?

Yes, you can generate a shareable markdown report by collecting the past week's commits and file changes. The report summarizes development patterns and hotspots suitable for sharing in sprint retrospectives.

Does this Git analysis workflow require any external dependencies or specific setup?

No external dependencies are required. The workflow relies on standard Git commands and simple analytics to collect commit history and generate the weekly retrospective report.

Why should I use automated Git history analysis instead of manual aggregation for retrospectives?

Automated Git history analysis prevents the tedious and error-prone nature of manual aggregation. It collects commits and analyzes hotspots automatically to produce a concise summary, saving time and improving accuracy.