retro

Analyze commit history and code quality to summarize team activity.

Updated Mar 22, 2026

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

Ready to run

npx skills add https://github.com/jeisenback/original-curse-killer --skill retro-jeisenback

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill retro-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives often miss opportunities to celebrate wins, surface growth areas, and align the team. This Skill automates the generation of a data-driven retro by analyzing commit history, code quality signals, and contributor momentum to produce clear narratives and targeted next steps.

Core Features & Use Cases

Per-person praise and growth opportunities derived from contribution patterns.
Persistent, date-range retros with trend comparisons and narrative storytelling.
Narrative-ready insights for team rituals and leadership reviews.

Quick Start

Ask Claude to run the retro skill for your desired window (e.g., /retro 7d) to generate a comprehensive retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a data-driven engineering retrospective from git history?▼

You can generate an engineering retro by analyzing git commit history and code quality signals over a specific time window. The retro skill automates this by summarizing contributor momentum and team trends into narrative reports.

What is the best way to analyze team engineering metrics for weekly growth opportunities?▼

Analyzing weekly engineering metrics involves evaluating commit history and contributor momentum over a time window. This approach surfaces per-person growth opportunities and team-wide trends for continuous engineering growth.

Can I compare engineering team activity across different time ranges?▼

Yes, you can compare engineering team activity across time ranges using the compare mode. It evaluates contributor momentum and commit history across windows ranging from 24 hours to 30 days to identify team trends.

How do I handle missing git data when summarizing contributor momentum for a team retro?▼

Handling missing git data during a retro requires robust edge case management. The retro skill processes incomplete commit history gracefully to ensure your team retrospective still generates structured narratives and metadata.

Does the retrospective analysis output structured metadata for downstream reporting?▼

Yes, the retrospective analysis outputs structured metadata for downstream reporting. This allows leadership reviews and external systems to consume the generated team trends and per-author growth opportunities directly.