retro

Name: retro
Availability: InStock
Author: abysscn

Analyze git history to generate engineering retrospective reports.

36|1|Updated Jun 4, 2026

Search Tags:#git #code review #productivity #analysis #retrospective

Ready to run

npx skills add https://github.com/AbyssCN/xihe --skill retro-abysscn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/AbyssCN/xihe/tree/main/skills/retro
Command: npx skills add https://github.com/AbyssCN/xihe --skill retro-abysscn

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The retro skill provides an analytical tool to gain insights from your git history, offering a summary of your development work and productivity trends over specified periods.

Core Features & Use Cases

Engineering Retrospective: Automatically generates a summary of your engineering activities, including commit types, focus score, test discipline, and productivity trends.
Timeframes: Supports analysis of specified periods like last 24 hours, 14 days, 30 days, or a comparison between two periods.
Data Visualization: Outputs a report detailing achievements, challenges, and opportunities for improvement, allowing teams to make data-driven decisions.

Quick Start

Start your engineering retrospective with the command: /retro

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 history?▼

Generate an engineering retrospective by running the /retro command, which analyzes your git history to summarize commit patterns, developer focus, and productivity trends over specified periods.

What is a git commit pattern analysis and how does it work?▼

Git commit pattern analysis automatically extracts data from your repository history to evaluate commit types, test discipline, and focus scores, providing data-driven insights into development activities.

Can I analyze developer productivity trends for a specific timeframe like a sprint?▼

You can analyze developer productivity trends for specific timeframes such as the last 24 hours, 14 days, 30 days, or by comparing two distinct periods to support sprint or weekly review processes.

Does the retrospective report include actionable insights for code review?▼

The retrospective report includes actionable insights by detailing achievements, challenges, and opportunities for improvement, allowing teams to make data-driven decisions during code review and sprint planning.

Do I need any external dependencies to analyze my git history?▼

You do not need external dependencies to analyze your git history, as the skill operates independently using built-in scripts and references to parse repository data and generate summary reports.