retro

Generates weekly engineering retrospectives from Git commit history and code metrics.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xuithoi/Claudecode_gtask --skill retro-xuithoi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/xuithoi/Claudecode_gtask/tree/main/retro
Command: npx skills add https://github.com/xuithoi/Claudecode_gtask --skill retro-xuithoi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive weekly engineering retrospectives, providing deep insights into team productivity, code quality, and individual contributions.

Core Features & Use Cases

  • Data-Driven Insights: Analyzes commit history, work patterns, and code quality metrics.
  • Team-Aware Analysis: Breaks down per-person contributions, offering praise and growth opportunities.
  • Trend Tracking: Compares current performance against historical data to identify improvements and regressions.
  • Use Case: Run /retro at the end of each week to get a detailed report on what the team accomplished, identify bottlenecks, celebrate wins, and pinpoint areas for improvement in the next sprint.

Quick Start

Run the retro skill to analyze the last 7 days of commits.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective from Git commit history?

Generate an engineering retrospective from Git commit history by running the analysis tool against your repository to extract author contributions, work patterns, and code quality metrics. It summarizes session activity and code hotspots into a detailed weekly report for actionable team insights.

Can I analyze per-contributor performance and code quality metrics for my team?

Analyze per-contributor performance and code quality metrics by running the retrospective tool against your repository's commit history. It breaks down individual author contributions, identifies work patterns, and highlights both growth opportunities and wins for the team.

What's the best way to track team performance trends using Git metrics?

Track team performance trends using Git metrics by running the retrospective analysis weekly to compare current output against historical data. This identifies bottlenecks, tracks code hotspots, and reveals work pattern regressions or improvements over time.

Do I need external dependencies to run a code analysis retrospective?

No external dependencies are required to run a code analysis retrospective. The tool directly parses Git commit history and author contributions from your repository to generate detailed weekly engineering reports without needing additional software packages.

How do I identify code hotspots and session activity in my repository?

Identify code hotspots and session activity by analyzing Git commit history with the retrospective tool. It processes commit patterns and author contributions to pinpoint frequently modified code areas and map out active development sessions.

When do I need to run a weekly retrospective report for sprint improvement?

Run a weekly retrospective report at the end of each week to analyze the last 7 days of Git commits. It identifies bottlenecks, celebrates wins, and pinpoints areas for improvement to optimize the next sprint using historical trend analysis.