retro

Analyze commit history and generate structured engineering retrospective reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, write, glob, askuserquestion, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the engineering retrospective process, saving time and providing insights to enhance team performance and collaboration.

Core Features & Use Cases

  • Automated Retro Analysis: Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking.
  • Team-aware Reports: Breaks down per-person contributions with praise and growth areas.
  • Use Case: Use it during weekly retrospectives, 'what did we ship' sessions, or 'engineering retro' discussions to facilitate meaningful conversations.

Quick Start

Use the /retro skill to analyze and report on your engineering project's past week activities.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate engineering retrospective meetings using commit history?

Automate engineering retrospective meetings by analyzing commit history and project information to generate structured team performance reports. The Skill evaluates work patterns and code quality metrics to provide insights for weekly feedback sessions.

What is automated project analysis for team retrospectives?

Automated project analysis for team retrospectives evaluates commit history and work patterns to break down per-person contributions. It identifies praise and growth areas, providing structured reports to facilitate meaningful engineering collaboration discussions.

Do I need filesystem access to analyze engineering project data for retros?

Yes, filesystem access is required to analyze engineering project data for retros. The Skill accesses commit history and project information directly from the filesystem to evaluate code quality metrics and generate trend tracking reports.

Can I track team performance trends over multiple weekly retrospectives?

Yes, you can track team performance trends over multiple weekly retrospectives. The Skill maintains persistent history of commit analysis and work patterns, enabling longitudinal trend tracking for engineering collaboration and growth evaluation.

What's the best way to prepare for a 'what did we ship' engineering session?

Prepare for a 'what did we ship' engineering session by running an automated commit history analysis. The Skill generates team-aware reports detailing per-person contributions, highlighting specific praise and growth areas for project analysis discussions.

Are there limitations when analyzing code quality metrics for team performance?

Analysis of code quality metrics for team performance requires direct filesystem access to project repositories. Limitations apply to administrative and collaboration workflows, focusing strictly on commit history data rather than external project management integrations.