retro

Name: retro
Availability: InStock
Author: concept2cure

Analyze repository commit history to generate weekly engineering retrospectives.

1|Updated Nov 13, 2025

Search Tags:#commit #analysis #metrics #engineering #growth #team #retro

Ready to run

npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill retro-concept2cure

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros help engineering teams analyze commit history, code quality metrics, and work patterns to surface praise and growth opportunities. It provides persistent history and per-person insights so teams can learn and improve over time.

Core Features & Use Cases

Per-person contribution analysis with praise and growth opportunities.
Time-window based retrospectives (7d default, 24h, 14d, 30d) and cross-project global retrospectives.
Proactive suggestions at the end of a work week or sprint to guide next steps and focus.

Quick Start

Ask Claude to run /retro to generate a weekly engineering retrospective for the current project.

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

Generate a weekly engineering retrospective by analyzing repository commit history to surface team contributions and code quality metrics. Run /retro to process the current project's git logs and produce per-author praise and growth insights for the default 7-day window.

What is a team-aware engineering retrospective and how does it work?▼

A team-aware engineering retrospective analyzes commit history to track per-author praise, growth opportunities, team alignment, and session patterns. It parses git logs across fixed windows to surface code quality metrics and actionable outcomes for the whole team.

Can I run a retrospective across multiple repositories or a global workspace?▼

You can run cross-project global retrospectives across multiple repositories or a multi-repo workspace. The analysis compares periods and tracks trends globally, evaluating team alignment and engineering growth across your entire codebase rather than a single project.

What time windows can I use for analyzing commit history and code quality metrics?▼

You can analyze commit history using fixed time windows of 24 hours, 7 days, 14 days, or 30 days. The 7-day window is the default for weekly retrospectives, while shorter or longer windows support daily check-ins or extended sprint analysis.

Does the retrospective analysis provide proactive suggestions for the next sprint?▼

The retrospective analysis provides proactive suggestions at the end of a work week or sprint to guide next steps and focus. These actionable outcomes are generated from commit patterns and code quality metrics to help the team learn and improve over time.

What are the limitations of using commit history for engineering growth analysis?▼

Commit history analysis for engineering growth relies on git data, capturing only coding activity and missing non-code contributions like design or planning. Retrospective insights are limited to per-author commit patterns and code quality metrics within the analyzed repositories.