retro

Analyze git commit history and code metrics to generate team retrospectives.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/esopian/blue-oak-audit --skill retro-esopian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/esopian/blue-oak-audit/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/esopian/blue-oak-audit --skill retro-esopian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps engineering teams analyze past work patterns, commit history, and code quality metrics to improve their workflows and identify areas for growth.

Core Features & Use Cases

  • Commit & Work Pattern Analysis: Tracks contributions and interactions within the team over time.
  • Trend Tracking & Visual Summaries: Provides historical insights on code quality and team activity.
  • Use Case: Prepare a weekly report summarizing who contributed most, common bottlenecks, and areas for technical improvement, all from repository data.

Quick Start

Ask for a summary of last week's engineering activity to see a quick overview of team contributions and code trends.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git commit history?

The retrospective process analyzes commit history, work patterns, and code metrics to identify contribution trends and quality issues. It extracts insights from git data, commit logs, and code quality metrics to inform team improvements during weekly reviews.

What is engineering retrospective trend analysis and how does it work?

Engineering retrospective trend analysis tracks contributions and code quality metrics over time. It evaluates commit logs and work patterns to provide historical insights on team activity, highlighting common bottlenecks and areas for technical improvement.

How do I track code quality trends and team contributions for weekly reviews?

Track code quality trends and team contributions by analyzing repository data and commit logs. This process provides visual summaries of historical insights on team activity and code metrics to prepare weekly reports summarizing who contributed most.

Can I analyze commit logs to identify engineering bottlenecks and contribution patterns?

Yes, analyzing commit logs identifies engineering bottlenecks and contribution patterns. The process tracks contributions and interactions within the team over time, extracting insights from git data to inform team improvements and prepare weekly reports.

Do I need specific git data formats to perform commit analysis for team retrospectives?

Performing commit analysis for team retrospectives requires git data, commit logs, and code quality metrics. The Skill extracts insights from these repository data sources to generate summaries of engineering activity and identify areas for growth.