skills.rest
uzumaki-inc
uzumaki-incOFFICIAL
Explore all skills by this author →
GitHub

retro

Aggregate git commit history and code quality metrics into weekly retrospectives.

Updated Apr 25, 2026
Search Tags:#git#analytics#metrics#engineering#code-quality#trends#retro
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill retro-uzumaki-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/uzumaki-inc/uzustack/tree/main/retro
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill retro-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams and solo builders conduct a consistent weekly retrospective by analyzing commits, work patterns, and code quality metrics to surface trends and actionable insights.

Core Features & Use Cases

  • Automated narrative of contributions by analyzing git history and author activity to highlight strengths and growth areas.
  • Time-window based retrospectives supporting current window comparisons, cross-team views, and personalized focus reports.
  • Narrative-generation and ready-to-share summaries for CTOs and ICs to communicate progress and risks.

Quick Start

Navigate to your project and run the retro workflow by invoking /retro to generate the weekly engineering retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly engineering retrospective from git history?▼

You can generate a weekly engineering retrospective by navigating to your project and invoking the retro workflow, which aggregates git commit history, author patterns, and code quality metrics into a structured summary.

What engineering metrics are needed to track code quality trends over time?▼

Tracking code quality trends requires analyzing git commit history, lines of code, test signals, and activity hotspots, which are aggregated into a JSON snapshot for window-based trend comparisons.

Can I use git analytics to create narrative summaries for leadership reviews?▼

Yes, git analytics can create narrative summaries for leadership reviews by aggregating weekly engineering activity and author contributions into ready-to-share reports highlighting progress and risks.

Does weekly engineering analytics support both solo developers and team contexts?▼

Weekly engineering analytics supports both solo developers and team contexts by providing window-based comparisons and personalized focus reports tailored to each working scope.

What is the best way to analyze commit patterns and hotspots for a project retrospective?▼

The best way to analyze commit patterns and hotspots for a project retrospective is to read origin default git data, compute activity metrics, and generate a structured narrative of contributions.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
ynulihaoynulihao
564

data-storytelling

Transform raw data into narratives with visualization and story structure.

Community
Basic
luokai25luokai25

test-automator

Develop test automation frameworks, scripts, and CI/CD pipeline integrations.

Community
Advanced
esopianesopian
2

gstack-openclaw-retro

Analyzes git commit history to generate weekly engineering retrospective reports.

Community
Advanced