retro

Analyzes commit history and code metrics to generate weekly engineering retrospectives.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill retro-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill retro-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack visibility into what actually shipped each week, how work patterns evolve, and where code quality is drifting. This Skill automates the weekly retrospective by mining git history, session data, and prior retro records into a structured report. ## Core Features & Use Cases - Commit and velocity analysis: Breaks down commits, LOC, PR sizes, fix chains, and shipping streaks across the team. - Team-aware breakdowns: Per-person contributions with praise and growth areas anchored in actual commits, plus AI-assisted commit percentages. - Trend tracking: Compares against prior retros stored in .context/retros/*.json to surface week-over-week changes in test health, focus, and plan completion. - Use Case: At the end of a sprint, ask for a weekly retro and receive a report covering shipping velocity, test health deltas, shortcut debt, top team wins, and three habits for next week. ## Quick Start Ask the assistant to run a weekly retro for this repository to generate the full engineering retrospective report.

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?

Invoke the retro skill with a phrase like "weekly retro" or "what did we ship". It analyzes commit history, LOC, PR sizes, and session patterns, then outputs a structured report with trends, team breakdowns, and habits for next week.

What metrics does an engineering retro report include?

The report covers commit counts, lines of code, test ratio, PR size distribution, fix chains, shipping streaks, focus scores, plan completion percentages, and shortcut debt. It also includes per-person breakdowns with praise and growth suggestions.

Does the retro skill track trends across multiple weeks?

Yes. It reads prior retros from .context/retros/*.json and compares current metrics against the last retro, showing deltas for test counts, velocity, and other signals. On first run it compares against a computed prior period.

Can the retro skill break down contributions per team member?

Yes. It produces a team breakdown sorted by commits, describing what each person shipped, specific praise anchored in real commits, and one constructive growth opportunity per teammate. Solo repositories skip this section.

What are the limitations of git-history-based retrospectives?

The analysis only sees what is committed, so uncommitted work, meetings, and design discussions are invisible. Metrics like LOC and commit counts are proxies for effort and should be read alongside the narrative sections, not as performance scores.