skills.rest
ekrishgupta
ekrishguptaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history and code quality metrics to generate engineering retrospectives.

1|3|Updated Mar 19, 2026
Search Tags:#git#analysis#metrics#engineering#focus#team#retro
One-click install
npx skills add https://github.com/ekrishgupta/gemstack --skill retro-ekrishgupta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ekrishgupta/gemstack/tree/main/retro
Command: npx skills add https://github.com/ekrishgupta/gemstack --skill retro-ekrishgupta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective analyzes commit history, work patterns, and code quality metrics to surface team-aware praise and growth opportunities, with persistent history and trend tracking.

Core Features & Use Cases

  • Analyzes per-contributor contributions with praise and growth areas.
  • Proactively suggests improvements and provides a narrative suitable for leadership.
  • Generates a team-wide retrospective with focus, hotspots, session patterns, and progress signals.

Quick Start

Run /retro to generate the weekly retrospective for the current window (default last 7 days).

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

You can generate an engineering retrospective by running the skill on your git repository, which analyzes commit history, contributor activity, and code quality metrics to produce a structured snapshot and narrative for the selected time window.

What metrics are included in a weekly engineering retrospective?▼

A weekly engineering retrospective includes lines of code (LOC), tests, session patterns, hotspots, focus highlights, and per-contributor praise and growth opportunities, surfacing team-wide insights and progress signals.

Can I analyze code quality and contributor activity for a custom time window?▼

Yes, you can analyze code quality and contributor activity for a custom time window instead of the default last 7 days, surfacing team-wide insights, focus highlights, and progress signals for your specified period.

Does the retrospective analysis work without external dependencies like greptile?▼

Yes, the retrospective analysis works without mandatory dependencies, utilizing optional greptile, backlog, and test-health signals when available to enhance the code quality metrics and engineering insights.

How do I surface per-person praise and growth opportunities from git metrics?▼

You surface per-person praise and growth opportunities by analyzing per-contributor contributions within your git repository, evaluating individual work patterns and code quality metrics to generate targeted feedback.

What is the best way to track team-wide progress signals and hotspots in software engineering?▼

The best way to track team-wide progress signals and hotspots is to run a retrospective that analyzes commit history and session patterns, delivering a comprehensive narrative and structured snapshot suitable for leadership review.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

retro

Analyze weekly commit history and code quality for team retrospectives.

Community
Advanced
uzumaki-incuzumaki-inc

retro

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

Official
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
gth-aigth-ai
1

retro

Analyze git commit history and code metrics to generate engineering retrospectives.

Community
Advanced