retro

Generate structured weekly retrospective narratives from git history, timelines, and learnings.

Updated Jun 18, 2026

Search Tags:#git #learning #retrospective #engineering #retro #team-performance

Ready to run

npx skills add https://github.com/abhishekmmgn/didactic-invention --skill retro-abhishekmmgn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill retro-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams reflect on recent work, surface praise and growth areas, and maintain a persistent history of learnings across sprints.

Core Features & Use Cases

Analyzes commit history, timelines, and learnings to surface team strengths, blockers, and improvement opportunities.
Generates per-contributor insights (praise, growth targets) and cross-project patterns for continuous improvement.
Provides a structured recap suitable for team sharing, planning, and post-mortems.

Quick Start

Run the retro skill weekly to generate a concise engineering retrospective from recent commits, timelines, and learnings.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I automate weekly engineering retrospectives from git history?▼

Automating weekly engineering retrospectives involves analyzing local git commit history, project timelines, and learnings logs to generate a structured narrative. The output surfaces per-contributor praise, growth opportunities, and cross-project patterns for continuous improvement.

What is a git retrospective and how does it surface team learnings?▼

A git retrospective is an automated analysis of commit history and project timelines that identifies engineering team strengths and blockers. It generates a structured recap with sections for praise, learnings, and action items suitable for team sharing and post-mortems.

Do I need a specific log format to generate engineering retrospective insights?▼

Yes, generating engineering retrospective insights requires local git history, timeline logs, and a learnings.jsonl file. These inputs are aggregated to analyze weekly sprints and project milestones, producing per-contributor insights and cross-project improvement patterns.

Can I use commit history to track per-contributor growth opportunities?▼

Yes, you can use commit history to track per-contributor growth opportunities by analyzing weekly engineering activity. The process aggregates commits and timeline logs to surface individual praise and targeted growth areas for continuous team improvement.

What's the best way to structure a sprint retrospective for engineering teams?▼

The best way to structure a sprint retrospective is to automate the aggregation of commit history and learnings into distinct sections. This generates a structured recap with dedicated areas for praise, learnings, and action items, ensuring persistent history across sprints.

When should I not use automated git history analysis for retrospectives?▼

Automated git history analysis for retrospectives is not suitable when local git history, timeline logs, or learnings.jsonl files are unavailable. It is designed for weekly sprints and project milestones, so it may not fit contexts lacking structured engineering activity logs.