retro

Compiles weekly engineering retrospectives from git history and code-quality metrics.

107|19|Updated Mar 23, 2026

Search Tags:#git #metrics #engineering #code-quality #retro #team-performance

Ready to run

npx skills add https://github.com/mr-daedalium/ostack --skill retro-mr-daedalium

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are hard to compile from raw git history and code metrics. This Skill analyzes commit history, work patterns, and code quality metrics to deliver a persistent, team-aware retrospective with praise and growth opportunities.

Core Features & Use Cases

Per-person contribution breakdown with praise and growth opportunities.
Team-wide trend analysis for commits, LOC, tests, hotspots, and focus patterns.
Narrative summaries that translate data into actionable improvements for sprints and releases.

Quick Start

Invoke the retro skill to generate the weekly retrospective for the default 7-day window.

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

Generate a weekly engineering retrospective by invoking the tool to analyze git commit history, work session patterns, and code-quality metrics. It compiles a structured snapshot tracking commits, insertions, deletions, and test activity for the default 7-day window.

Can I get per-author contribution insights and coaching feedback from git metrics?▼

Yes, per-author contribution breakdowns provide specific praise and growth opportunities derived from git metrics. It analyzes individual commit patterns and code quality to deliver targeted narrative summaries useful for team coaching and sprint improvements.

What code-quality and work pattern metrics are tracked for team trend analysis?▼

Team trend analysis tracks commits, lines of code inserted and deleted, test activity, code hotspots, and work session patterns. This comprehensive metric tracking ensures robust guardrails for analyzing engineering performance across a defined window.

Does this work for a 7-day sprint window or can I analyze a longer release cycle?▼

The default analysis window is a 7-day period designed for weekly retrospectives. It supports trend analysis across a defined window, allowing you to capture engineering work patterns and code-quality metrics for broader sprint and release cycles.

What's the best way to translate raw git commit data into actionable team improvements?▼

Translate raw git data into actionable improvements by generating narrative summaries that identify engineering hotspots and focus patterns. These summaries convert commit history and code-quality metrics into structured coaching insights for your team.

Why do my weekly code-quality metrics lack per-person praise and growth insights?▼

Metrics lack per-person insights when raw git history is not compiled into a team-aware retrospective. Analyzing individual work patterns and test activity against robust guardrails structures the data into specific praise and growth opportunities.