skills.rest
yamparalarahul27
yamparalarahul27COMMUNITY
Explore all skills by this author →
GitHub

retro

Generate weekly engineering retrospectives from Git commit history and metrics.

Updated Aug 23, 2026
Search Tags:#code quality#git#analytics#retrospective#developer productivity#team performance
One-click install
npx skills add https://github.com/yamparalarahul27/illu-ic --skill retro-yamparalarahul27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/yamparalarahul27/illu-ic/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/yamparalarahul27/illu-ic --skill retro-yamparalarahul27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

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

Core Features & Use Cases

  • Automated Data Collection: Gathers commit history, LOC, PRs, and more from Git.
  • Team-Aware Analysis: Breaks down contributions per-person, identifying praise and growth areas.
  • Trend Tracking: Compares current metrics against historical data to show progress.
  • Use Case: A CTO can run /retro at the end of each week to get an instant, data-driven overview of the engineering team's output, identify bottlenecks, and celebrate wins.

Quick Start

Run the retro skill for the last 7 days of activity.

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 from Git commit history?▼

You can automate weekly engineering retrospectives by analyzing Git commit history, code metrics, and contributor patterns to generate a detailed report identifying team performance and code quality trends.

Can I generate team performance reports that break down contributions per-person?▼

Yes, generating team performance reports breaks down contributions per-person to identify individual praise and growth areas, providing a data-driven overview of engineering output.

What is the best way to track code quality trends and developer productivity over time?▼

Tracking code quality trends and developer productivity involves comparing current Git metrics against historical data to show progress, identify bottlenecks, and highlight actionable insights.

Does the retrospective analysis support custom time windows for historical comparisons?▼

Yes, retrospective analysis supports custom time windows and historical comparisons, allowing you to gather commit history, LOC, and PRs for any specified period.

How do I get a data-driven overview of my engineering team's output at the end of the week?▼

Getting a data-driven overview of engineering team output involves running an automated retrospective that analyzes weekly Git activity to identify bottlenecks and celebrate wins.

What Git metrics are needed to identify bottlenecks and areas for code improvement?▼

Identifying bottlenecks and areas for code improvement requires Git commit history, lines of code, PRs, and code quality metrics gathered automatically for trend tracking.

Related Skills

Explore More Software Engineering Skills→
shekerkammashekerkamma

gstack-openclaw-retro

Automates weekly engineering retrospective metrics from git commit history with configurable windows and saved snapshots.

Community
Advanced
lyndonkllyndonkl
142

reviews-retros-reflection

Facilitate structured retrospective sessions using formats like Start/Stop/Continue and 5 Whys.

Community
Advanced
shogo-labsshogo-labs
12

dev-activity-track

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

Official
Advanced
manager-dot-devmanager-dot-dev
104

developer-productivity

Analyze engineering delivery metrics to identify productivity gaps and generate measurement setups.

Official
Intermediate