retro

Name: retro
Availability: InStock
Author: ehsaanark

Analyzes git history and team metrics to generate weekly retrospective narratives with growth recommendations.

Updated Mar 14, 2026

Search Tags:#git #narrative #metrics #retrospective #engineering #team #retro

Ready to run

npx skills add https://github.com/EhsaanArk/ai-signal-router --skill retro-ehsaanark

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/EhsaanArk/ai-signal-router/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/EhsaanArk/ai-signal-router --skill retro-ehsaanark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are often manual and hard to standardize. The retro skill provides a trigger-based workflow to analyze commit history, work patterns, and code quality metrics, delivering a consistent, team-focused reflection with growth opportunities.

Core Features & Use Cases

Manual trigger on /retro to generate a team-focused retrospective.
Analyzes commits, contributor patterns, and quality metrics with per-person praise and growth opportunities.
Produces a narrative summary and actionable recommendations for teams.

Quick Start

Type /retro to generate the weekly engineering retrospective for 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 generate a weekly engineering retrospective from git history?▼

Generate a weekly engineering retrospective by triggering the command manually. It analyzes your git commit history, computes per-author contributions, and outputs a narrative summary with actionable growth guidance for the team.

What is included in a sprint review based on contributor patterns?▼

A sprint review based on contributor patterns includes per-author contributions, work patterns, and code quality metrics. It delivers a team-focused reflection with specific praise and growth opportunities for each member.

Can I use this retro workflow for a custom time window longer than a week?▼

The retro workflow defaults to a 7-day window for analyzing engineering activity and code quality. You trigger it manually to summarize weekly metrics, though historical retrospectives are persisted for future reference.

What's the best way to standardize what we shipped during the last sprint?▼

The best way to standardize what you shipped is using a trigger-based workflow that analyzes commits and team-wide metrics. It produces a consistent, narrative summary of engineering activity and actionable recommendations.

Do I need to integrate external tools to track code quality metrics for a team retro?▼

No external tools are needed for code quality metrics in a team retro. The workflow analyzes git history, contribution patterns, and quality metrics directly to deliver per-person praise and growth opportunities.