retro

Analyze git history and metrics to generate engineering retrospectives with per-author praise and growth.

33|6|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/WillNigri/Agentic-Tool-Optimization --skill retro-willnigri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/WillNigri/Agentic-Tool-Optimization/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/WillNigri/Agentic-Tool-Optimization --skill retro-willnigri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, per-author praise/growth, and team patterns to inform focus and improvements.

Core Features & Use Cases

  • Generates end-to-end retrospectives with per-author breakdowns.
  • Computes focus scores, ship-of-the-week, and streak tracking.
  • Provides a narrative and actionable suggestions for teams.

Quick Start

Run the retro skill to generate a weekly engineering retrospective for the past 7 days.

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?

An engineering retrospective analyzes your team's git history over a defined window to generate per-author praise, growth opportunities, and team-wide patterns. The retro skill produces a narrative plus structured data suitable for review and later history saving.

What metrics are included in a team performance retrospective?

A team performance retrospective includes per-author contributions, test activity, hotspots, PRs, sessions, and focus metrics. It also computes focus scores, ship-of-the-week, and streak tracking to provide actionable suggestions for engineering teams.

Can I analyze individual developer contributions for a specific time window?

Yes, you can analyze individual developer contributions for a specific time window. The retro skill scopes origin/<default> git history to your selected window and generates per-author breakdowns including praise and growth opportunities for each team member.

How does automated code quality analytics work for weekly reviews?

Automated code quality analytics for weekly reviews works by examining git commit history, test activity, and PRs to compute focus scores and identify hotspots. It then generates a narrative with actionable suggestions for continuous improvement.

Do I need any external dependencies to run a git collaboration analytics retrospective?

No external dependencies are required to run a git collaboration analytics retrospective. The retro skill operates independently to analyze your repository's development activity and generate structured engineering retrospectives.