retro

Analyze commit history and code quality metrics to generate weekly retrospective insights.

Updated May 14, 2026
One-click install
npx skills add https://github.com/lemig/transcriptor --skill retro-lemig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/lemig/transcriptor --skill retro-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are often inconsistent, manual, and lose historical context. This Skill automates collection of commit history, work patterns, and code-quality signals across weeks to produce a structured, searchable retro that surfaces praise and growth opportunities.

Core Features & Use Cases

  • Persistent weekly retros with per-person breakdowns and growth suggestions.
  • Trend tracking across sprints: ships, quality metrics, and collaboration signals.
  • Readable outputs suitable for team reviews and LLM-based analysis.

Quick Start

Ask the retro skill to generate this week's retrospective for the current sprint.

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 using commit history and code quality metrics?▼

Automate weekly engineering retrospectives by analyzing commit history, work patterns, and code quality signals to generate structured per-person contributions, praise, and growth areas with trend context.

What is sprint trend analysis and how does it track team growth across release cycles?▼

Sprint trend analysis tracks ships, quality metrics, and collaboration signals across release cycles to maintain historical context and surface continuous team growth opportunities.

Do I need persistent history storage and repository metrics to generate retrospective insights?▼

Yes, generating retrospective insights requires access to persistent history storage and repository metrics like commits, PRs, and static analysis signals to compute outputs.

How do I generate a retrospective for the current sprint?▼

Generate a retrospective for the current sprint by applying the analysis to weekly sprint data, which produces readable outputs suitable for team reviews and LLM-based analysis.

Can I track code quality and work patterns across multiple sprints without losing historical context?▼

Yes, you can track code quality and work patterns across multiple sprints without losing context because the Skill persists weekly retros with historical trend tracking.