skills.rest
greglas75
greglas75COMMUNITY
Explore all skills by this author →
GitHub

retro

Generate engineering retrospectives from git metrics, backlog state, and skill usage logs.

6|Updated Mar 27, 2026
Search Tags:#retrospective#engineering analytics#deployment frequency#git metrics#backlog health#churn hotspots#release report
One-click install
npx skills add https://github.com/greglas75/zuvo --skill retro-greglas75
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/greglas75/zuvo/tree/main/skills/retro
Command: npx skills add https://github.com/greglas75/zuvo --skill retro-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lack a data-driven view of how a release period actually went. This Skill turns git history, backlog files, and skill usage logs into a narrative retrospective report with concrete actionable items, replacing manual metric gathering. ## Core Features & Use Cases - Git Metrics: Computes deployment frequency from release tags, release cycle span, and top-5 churn hotspot files for a detected or explicit commit range. - Backlog & Quality Trends: Reads memory/backlog.md for open, critical, and resolved items, and aggregates CQ/Q scores and pass/fail verdicts from the skill usage log. - Actionable Report: Writes a structured Markdown report to zuvo/reports/ with at least three derived action items and a delta comparison against the prior retro. - Use Case: After shipping v1.2.0, run the retro to learn that src/orders/service.ts changed 12 times without tests, then get a suggested zuvo:write-tests command. ## Quick Start Ask the assistant to run the retro skill for the range v1.1.0..v1.2.0 to generate the 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 an engineering retrospective from git history?▼

Run the retro skill with an optional git range like v1.0.0..v1.2.0 or a --since tag. It auto-detects the window from memory/last-ship.json or the last two git tags when no argument is given, then produces a narrative report with actionable items.

What metrics does a git-based retrospective report include?▼

The report covers deployment frequency from release tags, release cycle span in days, top-5 churn hotspot files, backlog open/critical/resolved counts, and average CQ and Q quality scores with pass/fail ratios from the skill usage log.

Does the retro skill work in a monorepo?▼

Yes. It detects turbo.json, nx.json, or pnpm-workspace.yaml and either auto-scopes to a single touched package or analyzes all affected packages. Pass --path <dir> to scope git analysis to one package explicitly.

What happens if my repository has very few commits?▼

If the window contains fewer than 10 commits, the skill flags insufficient history and produces a qualitative-only report. It skips git metrics and skill trends, using backlog health as the sole data source while still generating actionable items.

Where is the retrospective report saved?▼

Reports are written to zuvo/reports/ with a filename like retro-YYYY-MM-DD-<previousTag>_<newTag>.md, falling back to short SHA suffixes when tags are unavailable. The directory is created if it does not exist.

Related Skills

Explore More Software Engineering Skills→
yashs33244yashs33244
1

gstack-openclaw-retro

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

Community
Advanced
chrisbaneschrisbanes
908

compose-stability-diagnostics

Diagnose and fix parameter stability issues in Jetpack Compose.

Community
Advanced
SoSoBurnerSoSoBurner

gstack-openclaw-retro

Analyze git commit history and code quality metrics for engineering retrospectives.

Community
Advanced
dangernoodle-iodangernoodle-io

recall

Query ouroboros for project context across knowledge base, backlog, and plans.

Official
Intermediate