retro

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

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill retro-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-retro
Command: npx skills add https://github.com/drt0927/tw-overlay --skill retro-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are tedious and inconsistent. This skill analyzes commit history, work patterns, and code quality metrics with a persistent history and team-aware growth notes to surface actionable insights.

Core Features & Use Cases

  • Team-aware retrospectives that highlight per-person contributions and growth opportunities.
  • Persistent history with trend tracking across sprints and releases.
  • Proactive prompts to initiate reflection at the end of a work week or sprint.

Quick Start

Invoke /retro to generate the weekly engineering retrospective with 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 automate weekly engineering retrospectives from git commit history?

Automate weekly retrospectives by analyzing git commit history and code quality metrics to generate a structured narrative with per-person praise, growth notes, and actionable improvement areas. Invoke the tool to process a default 7-day window automatically.

What is a team-aware software retrospective and how does it track sprint trends?

A team-aware software retrospective highlights individual contributions and growth opportunities while maintaining persistent history. It tracks trends across sprints by comparing current versus prior windows to surface actionable engineering insights.

Can I generate per-person praise and growth notes for my software engineering team?

Generate per-person praise and growth notes by analyzing individual commit history and work patterns. The retrospective output identifies specific team member contributions, trends, and tailored areas for improvement during weekly sprints.

Does the automated retrospective output include discussion prompts for sprint reflection?

The automated retrospective output includes proactive discussion prompts to initiate team reflection at the end of a work week or sprint. It provides a structured narrative designed to guide meaningful engineering conversations.

What git data access is needed to analyze code quality metrics for sprint retrospectives?

Access to repository history is required to analyze code quality metrics and commit patterns for sprint retrospectives. The tool processes this git data to evaluate work patterns, identify trends, and generate comprehensive engineering learnings.