retro

Analyze commit history and quality metrics to generate weekly engineering retrospectives.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/diiviikk5/rezops --skill retro-diiviikk5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/diiviikk5/rezops/tree/main/retro
Command: npx skills add https://github.com/diiviikk5/rezops --skill retro-diiviikk5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with persistent history and trend tracking, providing per-person contributions and growth insights.

Core Features & Use Cases

  • Weekly retrospective generation with team-aware breakdown by contributor, trends, and quality signals.
  • Persistent history across sprints to track improvements and recurring issues.
  • Use cases: when asked to summarize what shipped this week, identify hotspots, and highlight praise and growth areas.

Quick Start

Ask Claude to run a retro for the current sprint and generate a team-wide summary with per-person contributions and trend insights.

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

To generate a weekly engineering retrospective, the skill analyzes commit history, work patterns, and code quality metrics to produce a team-wide summary with per-person contributions, praise, and growth areas.

Can I track engineering sprint trends and recurring issues across multiple sessions?

Yes, you can track sprint trends across sessions because the skill maintains persistent history, allowing you to monitor improvements, identify recurring issues, and observe quality signals over time.

What is the best way to summarize what shipped during a weekly sprint?

The best way to summarize what shipped during a weekly sprint is to run a retro, which applies deterministic data gathering to your release cycles and delivers a clear narrative with actionable recommendations.

Does this retrospective tool provide per-person contributions and growth insights?

Yes, this retrospective tool provides per-person contributions and growth insights by generating a team-aware breakdown that highlights individual praise and specific growth areas for each contributor.

How do code quality metrics factor into sprint retrospectives?

Code quality metrics factor into sprint retrospectives by acting as quality signals that the skill evaluates alongside commit history and work patterns to identify hotspots and guide actionable improvements.