retro

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

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill retro-makyua-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill retro-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lose track of progress and patterns across weeks. The retro skill analyzes commit history, work patterns, and code quality metrics to surface a cohesive, per-person narrative with praise and growth opportunities, helping teams learn and improve over time.

Core Features & Use Cases

  • Per-person contributions breakdown with praise and growth areas to guide individual development.
  • Persistent history and trend tracking across weeks to reveal patterns in shipping, quality, and collaboration.
  • Proactive prompts at week/sprint end suggesting concrete actions to improve the next cycle.

Quick Start

Ask Claude to generate the weekly retro for the last 7 days from the repository data and present per-person insights with concrete growth actions.

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?

Generate a weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics to surface per-person contributions with praise and growth opportunities. The retrospective provides actionable insights and a narrative suitable for sharing with the team.

What is a per-person engineering retrospective and how does it improve team growth?

A per-person engineering retrospective analyzes individual contributions within commit history to guide development. It provides a team-aware breakdown highlighting praise and growth areas for each person, helping teams learn and improve over time.

Can I track code quality trends across multiple weekly retrospectives?

Yes, you can track code quality trends across weeks. The retrospective maintains persistent history and trend tracking to reveal patterns in shipping, quality, and collaboration, allowing targeted improvements over time.

How do I get concrete growth actions from code quality metrics at sprint end?

Get concrete growth actions at sprint end through proactive prompts suggesting specific improvements for the next cycle. The retrospective analyzes work patterns and code quality metrics to surface actionable insights for per-person development.

Does the weekly retrospective work for individual developer insights or only team-level analysis?

The weekly retrospective works for both levels by providing a team-aware breakdown of per-person contributions. It analyzes individual commit history and work patterns to surface praise and growth opportunities while maintaining a cohesive team narrative.