skills.rest
andrew-t-james
andrew-t-jamesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze the last 7 days of commits to generate a structured team retrospective.

Updated Jul 3, 2025
Search Tags:#commit#analysis#retrospective#engineering#growth#team#retro
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill retro-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/retro
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill retro-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that summarize commit history, work patterns, and team dynamics to identify praise and growth areas for the team.

Core Features & Use Cases

  • Team-aware retrospectives: analyzes contribution patterns and outcomes to surface meaningful praise and actionable growth opportunities.
  • Commit-driven insights: correlates what was shipped with team behavior to highlight improvements for the next cycle.
  • Use Case: at the end of a sprint, run this to auto-generate a structured retrospective that guides next-week planning.

Quick Start

Run the retro skill with /retro to generate the weekly engineering retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a team retrospective from recent commit history?▼

You can generate a weekly retrospective by analyzing the last 7 days of commit history and team activity, which surfaces top contributors, work patterns, and concrete next steps for improvement.

What is a commit-driven engineering retrospective?▼

A commit-driven engineering retrospective correlates what was shipped with team behavior to identify meaningful praise and actionable growth opportunities for the next development cycle.

How do I run a weekly engineering retrospective for sprint-end reviews?▼

Run the retrospective skill using the /retro command to auto-generate a structured narrative that highlights contribution patterns and guides next-week sprint planning.

Can I use commit analysis to surface team growth areas and praise?▼

Yes, commit analysis applies contribution patterns and outcomes to surface meaningful praise for top contributors and actionable growth areas for the engineering team.

Do I need any external dependencies to analyze team activity for retrospectives?▼

No external dependencies are required to analyze team activity, as the retrospective skill operates independently to review commit history and generate a structured narrative.

What's the best way to summarize engineering work patterns for leadership reflections?▼

The best way to summarize work patterns for leadership reflections is generating a structured retrospective that correlates shipped commits with team behavior to highlight improvements.

Related Skills

Explore More Software Engineering Skills→
agatxagatx
5

retro

Analyze git history to generate engineering retrospective reports with per-author metrics.

Community
Advanced
anishs1207anishs1207
1

retro

Analyze weekly git history to generate retrospective insights and trend analyses.

Community
Advanced
256javy256javy

retro

Aggregate commit history and code quality metrics into weekly engineering retrospectives.

Community
Advanced
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced