retro

Generates weekly engineering retrospective reports from git commit history and code quality signals.

Updated Apr 26, 2026

Search Tags:#git #narrative #metrics #engineering #retro #team-analysis

Ready to run

npx skills add https://github.com/XinheLIU/human-leverage --skill retro-xinheliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill retro-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Collects and interprets a week's worth of engineering activity to surface team-wide insights and personalized growth opportunities, turning churned commits and notes into a clear narrative.

Core Features & Use Cases

Team-aware per-person analysis with praise and actionable growth recommendations.
Automated synthesis from git history, code quality signals, and activity timelines to produce a comprehensive retrospective.
Shareable narrative and metrics to guide planning, reviews, and process improvements.

Quick Start

Type the /retro command to generate a weekly engineering retrospective for the past 7 days.

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 signals. The tool synthesizes activity timelines into a narrative with per-person praise and actionable growth recommendations for the team.

Can I analyze engineering work patterns for a custom time window like 24h or 30d?▼

Yes, you can analyze engineering work patterns for custom time windows. The tool applies to the current repository window by default 7 days, or supports user-specified windows like 24h, 14d, and 30d for flexible activity analysis.

What is included in a team-wide engineering narrative retrospective?▼

A team-wide engineering narrative retrospective includes synthesized commit history, code quality signals, and activity timelines. It provides machine-readable metrics alongside a human-friendly narrative with per-person praise and actionable growth opportunities.

Does the retrospective analysis handle edge cases in repository commit logs?▼

Yes, the retrospective analysis ensures robust handling of edge cases in repository commit logs. It processes git history and activity timelines to provide clear metrics and narrative interpretations even with irregular or sparse commit data.

What's the best way to summarize code quality signals for a development team?▼

The best way to summarize code quality signals is to extract metrics from recent commit history and activity timelines. This generates a comprehensive retrospective offering team-wide insights and personalized growth recommendations for developers.