skills.rest
giljae
giljaeCOMMUNITY
Explore all skills by this author →
Website𝕏@giljaeGitHub

retro

Generates retrospective reports from Git commit history and team metrics.

1|Updated Apr 5, 2026
Search Tags:#code quality#git analysis#team productivity#engineering retrospective#developer metrics#team growth
One-click install
npx skills add https://github.com/giljae/gstack-antigravity --skill retro-giljae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/giljae/gstack-antigravity/tree/main/gstack-origin/retro
Command: npx skills add https://github.com/giljae/gstack-antigravity --skill retro-giljae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams analyze their weekly or periodic development activities, highlighting trends and areas for improvement.

Core Features & Use Cases

  • Comprehensive Activity Analysis: Evaluates commit history, code quality metrics, and work patterns to understand productivity.
  • Team Recognition and Growth Opportunities: Identifies individual contributions and suggests improvements.
  • Use Case: A team lead wants to review commit trends, prioritize refactoring, and recognize top performers to guide next steps.

Quick Start

Ask the AI to generate a weekly engineering retrospective by saying "/retro" and optionally specify the time window, e.g., "/retro 14d" for two weeks of data.

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

To generate an engineering retrospective from git commit history, invoke the /retro command and optionally specify a time window like /retro 14d to analyze two weeks of data for your report.

What is an engineering retrospective and how does it use developer metrics?▼

An engineering retrospective uses developer metrics and git data to analyze recent team activity, identify workflow bottlenecks, and highlight key wins for continuous team growth.

Can I review team productivity and code quality trends over a specific time window?▼

Yes, you can review team productivity and code quality trends by specifying a time window when running the retrospective, allowing you to evaluate work patterns and contributions for that period.

How do I identify team bottlenecks and recognize top performers using git data?▼

You identify team bottlenecks and recognize top performers by analyzing commit history and code quality metrics, which evaluates individual contributions and spots patterns to guide next steps.

What's the best way to analyze code quality and work patterns for continuous improvement?▼

The best way to analyze code quality and work patterns for continuous improvement is running periodic retrospectives that evaluate commit trends, identify strengths, and suggest refactoring priorities.

Do I need any specific tools or integrations to track developer metrics for a retrospective?▼

No specific tools or integrations are required as dependencies to track developer metrics; the retrospective analyzes existing git data, code analysis, and team activity patterns directly.

Related Skills

Explore More Software Engineering Skills→
khapn-2933khapn-2933

tkm:run-retro

Generate sprint retrospective reports from git repository history.

Community
Advanced
hilaryosbornehilaryosborne

tl-retro

Facilitate team retrospectives to identify SMART action items for process improvement.

Community
Intermediate
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
shogo-labsshogo-labs
12

dev-activity-track

Aggregate GitHub commits, PRs, and reviews into per-developer dashboards.

Official
Advanced