retro

Analyze weekly commit history and code quality for team retrospectives.

Updated Mar 24, 2026

Search Tags:#git #analytics #productivity #engineering #teamwork #retro

Ready to run

npx skills add https://github.com/imonmi/INTER-EDU --skill retro-imonmi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives help teams reflect on the last iteration, identify patterns, celebrate contributions, and highlight growth areas. This tool automates analysis of commit history, work patterns, and code quality metrics to produce a persistent, team-aware narrative.

Core Features & Use Cases

Auto-analyzes commit history, work patterns, and code quality with per-person praise and growth suggestions.
Produces team-wide insights with persistent history and trend tracking, and can break down outputs per contributor.
Use when asked for "weekly retro", "what did we ship", or "engineering retrospective", and deploy proactive end-of-week summaries.

Quick Start

Run the retro command to generate a summary for the last 7 days, then review the per-contributor insights and growth areas.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate a weekly engineering retrospective from Git commit history?▼

Automating a weekly engineering retrospective aggregates Git commit history, work patterns, and code quality metrics to generate team-aware insights with per-contributor praise and growth suggestions.

Can I run a cross-project sprint retrospective that aggregates multiple repositories?▼

Cross-project sprint retrospectives analyze activity across multiple repositories, aggregating commit history and code quality metrics to identify team-wide trends and per-contributor growth areas.

Do I need Git access to generate per-contributor metrics and trend history?▼

Git access to the repository is required to analyze commit history and work patterns, enabling the generation of per-contributor metrics and persistent trend history.

What's the best way to track engineering team work patterns and code quality over time?▼

Tracking engineering work patterns and code quality over time requires aggregating weekly commit history into a persistent trend history, highlighting team-wide praise and growth areas.

How do I generate an end-of-week shipping summary for my engineering team?▼

Generate an end-of-week shipping summary by running the retro command to analyze the last 7 days of engineering activity, outputting per-contributor metrics and team-wide insights.