retro

Generate weekly engineering retrospectives from Git data and test results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lose sight of aggregate progress over time, struggle to extract actionable insights from weekly activity, and end up repeating issues. This Skill generates a clear, objective weekly retrospective that centers the engineering team's work.

Core Features & Use Cases

  • Aggregate commit history, PRs, tests, and code quality metrics to produce a concise retrospective.
  • Break down contributions per person with praise and growth recommendations.
  • Provide trend insights and concrete improvement suggestions to inform sprint planning.

Quick Start

Run the retro skill at the end of the sprint to generate a concise weekly retrospective with per-person 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 git history?

To generate a weekly engineering retrospective, the Skill aggregates git commit history, PRs, and test results to produce a concise summary of team progress and actionable insights.

Can I analyze code quality metrics and team contributions across multiple repos?

Yes, you can analyze code quality metrics and team contributions across multiple repos. The Skill processes multi-repo projects to provide per-person contribution breakdowns and growth recommendations.

What data do I need to provide per-person contribution breakdowns for a sprint?

To provide per-person contribution breakdowns, you need access to Git data, test results, and a persistent history store to track trends over time.

How does a sprint retrospective help with sprint planning?

A sprint retrospective informs sprint planning by providing trend insights and concrete improvement suggestions derived from analyzing aggregate commit history and code quality metrics.

Why do I need a persistent history store to track code quality trends?

You need a persistent history store to track code quality trends because the Skill compares current sprint metrics against historical data to generate objective growth recommendations and identify recurring issues.

What is the best way to extract actionable insights from weekly git activity?

The best way to extract actionable insights from weekly git activity is to aggregate commit history, PRs, and tests to automatically generate per-person praise and improvement suggestions.