retro

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

Updated Mar 30, 2026

Search Tags:#git #metrics #engineering #retro #leaderboard #team-feedback

Ready to run

npx skills add https://github.com/mulyoved/awesome-agent-ides --skill retro-mulyoved

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/mulyoved/awesome-agent-ides/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/mulyoved/awesome-agent-ides --skill retro-mulyoved

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros analyze commit history, work patterns, and code quality metrics to surface team-level insights, praise, and growth opportunities in a repeatable format.

Core Features & Use Cases

Team-aware retrospectives that break down contributions per person and highlight trends in work patterns, quality, and velocity.
Proactive suggestions at the end of a sprint or week to guide improvements and focus areas.
Leaderboard-style summaries showing per-author activity, hotspots, and suggested growth paths for engineers.

Quick Start

Type /retro to generate a weekly engineering retrospective for the last 7 days, or add a window like /retro 14d for a longer view.

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

Generate a weekly engineering retrospective by analyzing git commit history, work patterns, and code quality metrics to surface team-level insights, praise, and growth areas. Type /retro to produce a structured team-aware report for the last 7 days by default.

Can I run a retrospective covering a longer time window like 14 or 30 days?▼

Yes, you can run a retrospective for longer time windows. The default window is 7 days, but you can specify alternative periods like 24h, 14d, or 30d to analyze extended commit history and work pattern trends for your team.

Does the retro analysis support cross-project global retrospectives?▼

Yes, the retro analysis supports cross-project global retrospectives. It reads git data across multiple projects to deliver per-author leaderboards and trend analysis, providing a comprehensive view of team contributions and code quality metrics.

What data sources do I need to produce team feedback and leaderboards?▼

You need git commit history to produce team feedback and leaderboards. The analysis also reads optional greptile history and optional TODOS.md data when present, integrating these sources to output structured insights suitable for planning and team feedback.

How does the engineering retro identify praise and growth areas for developers?▼

The engineering retro identifies praise and growth areas by analyzing commit history, work patterns, and code quality metrics. It produces team-aware summaries with per-author leaderboards, highlighting activity hotspots and suggesting proactive improvement paths for engineers.

Can I use this retrospective tool for sprint planning and improvement suggestions?▼

Yes, you can use this retrospective tool for sprint planning. It provides proactive suggestions at the end of a sprint or week to guide improvements and focus areas, delivering structured insights from git metrics that are suitable for planning and team feedback.