skills.rest
Analog-Labs
Analog-LabsOFFICIAL
Explore all skills by this author →
Website𝕏@OneAnalogGitHub

retro

Analyze git history to generate weekly engineering retrospectives with per-author insights.

Updated Feb 28, 2026
Search Tags:#git#analysis#metrics#engineering#team#retro
One-click install
npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill retro-analog-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/Analog-Labs/pixelport-launchpad/tree/main/.agents/skills/gstack/retro
Command: npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill retro-analog-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams understand how code was shipped, who contributed, and where processes can improve, turning raw commits into actionable growth.

Core Features & Use Cases

  • Analyze commit history and work patterns to surface praise, growth opportunities, and trend lines.
  • Generate per-author insights and team-wide narratives to inform planning and process improvements.
  • Proactively suggest focus areas at the end of a sprint or week to accelerate maturation.

Quick Start

Run /retro to generate a weekly engineering retrospective 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 running /retro to parse raw git commit history from the last 7 days into narratives of who shipped what and how code quality evolved.

What is an engineering retrospective and what metrics does it analyze?▼

An engineering retrospective analyzes raw git history to surface work patterns, per-contributor praise, growth opportunities, and team-wide trend lines for sprint planning and process improvements.

Can I analyze individual contributor performance and team-wide trends separately?▼

You can analyze both separately. The retrospective generates per-author insights showing individual growth opportunities alongside team-wide narratives to inform broader planning.

Does the retrospective analysis work across custom time windows or only weekly?▼

Retrospective analysis applies across custom time windows, not strictly weekly. It collects, parses, and aggregates git metrics to proactively suggest focus areas at the end of any sprint or period.

What's the best way to track code quality evolution and team maturation?▼

Track code quality evolution by applying retrospective insights across time windows. The analysis surfaces team-wide trends and proactively suggests focus areas to accelerate maturation at sprint end.

Related Skills

Explore More Software Engineering Skills→
ericdahl-devericdahl-dev

gstack-openclaw-retro

Generate weekly engineering retrospectives from git commit history and code quality metrics.

Official
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

checkin

Verify build status, tests, code quality, and workflow compliance before committing.

Community
Intermediate
AbyssCNAbyssCN
36

retro

Analyze git history to generate engineering retrospective reports.

Community
Intermediate