retro

Analyze Git commit history to generate weekly engineering retrospectives.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/RxFit/hub-overlay --skill retro-rxfit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/RxFit/hub-overlay/tree/main/hub/skills/gstack/retro
Command: npx skills add https://github.com/RxFit/hub-overlay --skill retro-rxfit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of conducting weekly engineering retrospectives, ensuring that all team members are informed about past contributions, areas for growth, and future focus areas.

Core Features & Use Cases

  • Comprehensive Retrospective: Analyzes commit history, work patterns, and code quality metrics to provide a comprehensive view of the team's performance.
  • Team Awareness: Identifies individual contributions, highlights praise, and suggests growth areas for each team member.
  • Customizable Time Window: Offers flexibility to review commits over a customizable time frame (e.g., last 7 days, 14 days, 30 days).
  • Global Perspective: Optionally perform a cross-project retro across all AI coding tools.

Quick Start

Run the /retro command to start the retrospective analysis.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives using commit history?

You can automate engineering retrospectives by analyzing commit history and team contributions to identify work patterns, code quality metrics, and individual contributions for a comprehensive weekly review. Simply run the /retro command to start the analysis.

What is engineering retro analysis and how does it work?

Engineering retro analysis evaluates team performance by parsing Git commit history to extract work patterns and code quality metrics. It identifies individual contributions, highlights praise, and suggests growth areas for team members.

Do I need Git integration to analyze team performance and code quality metrics?

Yes, Git integration is required for commit history analysis to generate team performance retrospectives. You also need configuration settings for personalization to accurately identify work patterns and individual contributions.

Can I customize the time window for commit analysis during a weekly review?

Yes, you can customize the time window for commit analysis to review work patterns over the last 7, 14, or 30 days. This flexibility ensures the weekly retrospective covers the exact timeframe needed for your team performance evaluation.

What is the best way to conduct a cross-project engineering retrospective?

To conduct a cross-project engineering retrospective, you can optionally perform a global perspective analysis across all AI coding tools. This aggregates commit history and code quality metrics from multiple projects into a single comprehensive review.

How to identify individual contributions and work patterns for a team retrospective?

You identify individual contributions and work patterns by analyzing commit history metrics through an automated retrospective process. This highlights specific praise and suggests targeted growth areas for each team member based on their code quality data.