skills.rest
agatx
agatxCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze git history to generate engineering retrospective reports with per-author metrics.

5|2|Updated Dec 27, 2025
Search Tags:#git#analytics#code-quality#commit-history#retro#team-metrics
One-click install
npx skills add https://github.com/agatx/serenada --skill retro-agatx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/agatx/serenada --skill retro-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospective synthesis of engineering work to align teams on what happened, what to improve, and how to plan next steps.

Core Features & Use Cases

  • Analyzes commit history, per-contributor patterns, and code quality signals to generate a narrative report.
  • Maintains a persistent history and highlights trends, with a team-aware breakdown and praise/growth suggestions.
  • Produces structured sections such as a personal focus deep-dive and team-wide highlights to inform planning.

Quick Start

Ask Claude to generate this week's retro for the last 7 days, or specify another window such as 14d or 30d, or use compare to see trends.

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

Generate an engineering retrospective from git commit history by analyzing repository activity within a specified time window. The tool outputs a structured narrative covering per-author metrics, focus areas, team wins, and actionable recommendations.

Can I compare git analytics across different time windows for my team?▼

Yes, you can compare git analytics across different time windows such as 7 days, 24 hours, 14 days, or 30 days. Comparing windows highlights persistent trends and shifts in team metrics, focus areas, and code quality signals over time.

What is included in a git-based team retrospective report?▼

A git-based team retrospective report includes per-author metrics, contributor patterns, code quality signals, team-wide highlights, and actionable growth suggestions. It provides a structured narrative with personal focus deep-dives to inform planning.

Does generating weekly code quality metrics require any external dependencies?▼

Generating weekly code quality metrics and commit history retrospectives requires no external dependencies. The tool directly analyzes repository activity and git history to produce its structured narrative reports.

When should I use automated commit history analysis for team planning?▼

Use automated commit history analysis for team planning when you need to align on what happened, what to improve, and next steps. It is ideal for weekly retrospectives, maintaining persistent history, and tracking team metrics trends.

Related Skills

Explore More Software Engineering Skills→
ManzuetiManzueti

cyberdart-openclaw-retro

Analyze commit history, code quality metrics, and PR metrics for engineering retrospectives.

Community
Advanced
SeaLion-hubSeaLion-hub

retro

Analyze commit history and contribution patterns to generate weekly engineering retrospective reports.

Community
Advanced
luanluan
4

pr-reviewers

Recommend pull request reviewers using code ownership, commit history, and review load.

Community
Intermediate
wodehwodeh

gstack-openclaw-retro

Aggregate commit history and code quality metrics into weekly engineering retrospectives.

Community
Advanced