retro

Name: retro
Availability: InStock
Author: tropeks

Analyze commit history and code metrics to generate weekly team retrospectives.

Updated Mar 26, 2026

Search Tags:#git #analytics #metrics #engineering #team #retro

Ready to run

npx skills add https://github.com/tropeks/Vitali --skill retro-tropeks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/tropeks/Vitali/tree/main/.claude/skills/gstack-retro
Command: npx skills add https://github.com/tropeks/Vitali --skill retro-tropeks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are hard to assemble from scattered notes, making it difficult for teams to surface what shipped, what didn’t, and why. This Skill consolidates commit history, code quality metrics, and collaboration signals into a concise, actionable retrospective.

Core Features & Use Cases

Per-contributor praise and growth opportunities derived from commit activity and test results.
Persistent history with trend tracking and cross-project comparisons to guide planning and process improvements.
Use Case: after a sprint, run /retro to generate a team-wide report showing top contributors, hotspot files, and suggested focus areas.

Quick Start

Run /retro to generate the weekly retrospective for the current project and time window.

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

Generate a weekly engineering retrospective by analyzing git commit history, code quality metrics, and collaboration signals to surface per-author contributions, hotspot files, and recommended improvements. Running the retro command produces a team-aware report ready for leadership review.

Can I run retrospectives across multiple repositories instead of just one project?▼

Yes, retrospectives can be applied to both single-repo and cross-project contexts to surface who shipped, hotspots, and growth opportunities across the team. Cross-project comparisons guide planning and process improvements using persistent trend tracking history.

What metrics are included in a team-aware engineering retrospective?▼

A team-aware engineering retrospective includes per-author contributions, focus areas, commit activity, test results, hotspot files, and collaboration signals. It derives per-contributor praise and growth opportunities to provide an end-to-end narrative with clear guardrails for leadership review.

How do I track engineering team performance trends over multiple sprints?▼

Track engineering team performance trends by running retrospectives that maintain persistent history with trend tracking and cross-project comparisons. This consolidates scattered notes and metrics to guide planning, showing top contributors and suggested focus areas over time.

What is the best way to prepare a leadership-ready engineering report after a sprint?▼

Prepare a leadership-ready engineering report by running a retrospective that analyzes commit history and collaboration signals to produce an end-to-end narrative. The report includes per-contributor praise, growth opportunities, and recommended improvements with clear guardrails.