retro

Analyze commit history and code quality metrics to generate weekly team retrospectives.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/FxHollow/100000mrr-landing --skill retro-fxhollow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill retro-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics to surface persistent trends, praise contributions, and identify growth opportunities. It provides team-aware summaries that help leaders and engineers understand what shipped and how the team is evolving over time.

Core Features & Use Cases

  • Analyzes commit history and team contributions to surface per-person praise and growth areas.
  • Tracks long-term trends in code quality and work patterns to inform process improvements.
  • Supports prompts like "weekly retro", "what did we ship", or "engineering retrospective" and can proactively suggest actions at the end of a sprint.

Quick Start

Ask Claude to generate a weekly retro for the last 7 days.

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?

Generate a weekly engineering retrospective by analyzing commit history, work patterns, and code quality metrics over the last 7 days. This produces a structured summary with per-person praise, growth opportunities, and actionable recommendations for leadership.

What is a team-aware weekly retro and how does it work?

A team-aware weekly retro analyzes commit history and code quality metrics to surface persistent trends and track team evolution. It provides per-person praise and identifies growth areas to help engineers understand what shipped.

How do I track code quality trends and team contributions over time?

Track code quality trends and team contributions by analyzing git history and work patterns to produce a weekly retrospective. This process maintains persistent history to inform long-term process improvements and identify individual growth opportunities.

Can I analyze individual developer growth areas from commit history?

Analyze individual developer growth areas from commit history by applying a weekly retrospective to the current project window. It evaluates work patterns and code quality metrics to provide per-person praise and targeted growth opportunities.

Does generating an engineering retrospective require external dependencies?

Generating an engineering retrospective requires no external dependencies. It analyzes the existing git history, work patterns, and code quality metrics within your project window to produce structured summaries.

What's the best way to summarize what we shipped this sprint for engineering leadership?

Summarize sprint deliverables for leadership by analyzing team contributions and commit history. This produces a structured retrospective with persistent history, highlighting per-person praise and actionable recommendations for engineering leaders.