retro

Generates weekly engineering retrospectives from git history and team performance data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives require compiling commit history, work patterns, and code quality metrics to provide a clear view of team performance. This Skill automates that process, delivering a structured retrospective with persistent history and per-person visibility.

Core Features & Use Cases

  • Analyzes commit history, work patterns, and code quality metrics to surface trends over time.
  • Breaks down per-person contributions with praise and growth opportunities.
  • Proactively suggests retrospective topics at sprint boundaries or end of week.

Quick Start

Type /retro to generate this week's engineering retrospective.

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 commit history?

Generate a weekly engineering retrospective by analyzing local git commit history, work patterns, and code quality metrics to produce a structured report with per-person visibility and persistent history for review.

What metrics are included in an engineering team retrospective?

An engineering team retrospective includes commit history analysis, work pattern trends, and code quality metrics, broken down into per-person contributions with praise and growth opportunities for structured review and planning.

Can I automate sprint boundary retrospective topic suggestions?

Yes, you can automate sprint boundary retrospective topic suggestions by analyzing local git history and project metrics to proactively surface relevant discussion topics at the end of a sprint or week.

How do I track per-person engineering contributions for a retro?

Track per-person engineering contributions by analyzing local git commit history and project metrics, which surfaces individual work patterns and code quality trends with praise and growth opportunities for each team member.

Do I need external tools to analyze git history for a project retrospective?

No external tools are needed to analyze git history for a project retrospective. The process relies on local git history and project metrics, executing via Bash with allowed tools to produce a structured output.

What's the best way to summarize what my engineering team shipped this week?

The best way to summarize what your engineering team shipped this week is analyzing local git history and code quality metrics to generate a structured retrospective with persistent history and per-person visibility.