retro

Generate weekly engineering retrospectives from git history and quality signals.

15|5|Updated May 17, 2026

Search Tags:#git #retrospective #engineering #team-collaboration #process-improvement #blameless #health-metrics

Ready to run

npx skills add https://github.com/cropsgg/skills --skill retro-cropsgg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/retro
Command: npx skills add https://github.com/cropsgg/skills --skill retro-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives distilled from git history and quality signals to drive improvement and accountability.

Core Features & Use Cases

Time-window analysis with default 7 days, overrideable.
Git analysis: commits, hot spots, and trends.
Quality signals: health scores and issue metrics to surface systemic friction.
Output: concise themes and concrete actions for the next iteration.

Quick Start

Initiate a weekly retro by analyzing the latest 7 days of commits and health signals to generate a structured report.

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

Yes, you can generate blameless retrospectives by analyzing git commit history and quality signals over a default 7-day window. The tool surfaces systemic friction and thematic insights without assigning individual blame, focusing instead on process improvements and actionable items.

What's the best way to surface engineering process improvements from commit history?▼

Surface process improvements by applying thematic analysis to git commits, issue metrics, and health scores. This approach identifies systemic friction points and trends across a sprint or project boundary, translating them into concrete actions for the next iteration.

Can I customize the time window for analyzing git commits during a sprint retrospective?▼

Yes, the time window for git commit analysis defaults to 7 days but is fully overrideable. You can adjust the window to align with specific sprint boundaries or project milestones to review relevant shipped features and incidents.

Does a blameless retrospective tool work for solo developers?▼

Yes, blameless retrospectives work for solo developers as well as teams. The tool analyzes individual commit history and quality signals to identify hot spots, track trends, and generate actionable items for personal process improvement at project boundaries.

How do health metrics and issue data integrate into a retrospective report?▼

Health metrics and issue data integrate into the retrospective report as quality signals that surface systemic friction. Combined with git commit analysis, these metrics provide a data-informed foundation for identifying themes and generating concrete actions for the next iteration.