retro

Analyze git history metrics to generate weekly engineering retrospectives with summaries and snapshots.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Andy-HNU/AndyClaw --skill retro-andy-hnu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-retro
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill retro-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics, providing team-wide insights and growth opportunities.

Core Features & Use Cases

  • Automated retrospectives: aggregates git history, contributor activity, hotspots, and quality metrics to tell a complete story.
  • Team-focused insights: surfaces per-person praise and growth opportunities to guide development.
  • Proactive recommendations: suggests actions at sprint or week end to drive improvements.
  • Flexible windows & comparisons: supports last 7d, 24h, 14d, 30d, and compare modes.

Quick Start

Invoke /retro to generate the latest weekly retrospective for the default 7-day window.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a data-driven weekly engineering retrospective from git history?

To generate an engineering retrospective, you can analyze your team's git commits, contributor activity, and code quality metrics to automatically produce a narrative summary with per-author insights and growth opportunities.

Can I analyze git commits for a custom time window like the last 24 hours or 30 days?

Yes, you can analyze git commits and engineering metrics for flexible time windows including the last 24 hours, 7 days, 14 days, or 30 days, and use a compare mode to contrast metrics against a prior period.

What metrics are included in a team engineering retrospective?

A team engineering retrospective includes parsed git commits, author activity, code hotspots, test data, and optional telemetry to provide team-wide insights and surface per-person praise and growth opportunities.

How do I compare engineering metrics between two different time periods?

You can compare engineering metrics between two periods by using the compare mode, which contrasts your selected window against a prior period to highlight changes in git activity, hotspots, and test data.

Do I need any external dependencies or components to run a git retrospective?

No external dependencies or components are required to run a git retrospective; it directly parses your git history, author activity, and optional telemetry to generate the weekly engineering report.

How does automated retrospective analysis identify team growth opportunities?

Automated retrospective analysis identifies team growth opportunities by parsing commit history and code hotspots, then surfacing proactive recommendations and per-person feedback to guide development at sprint or week end.