skills.rest
pistosmin
pistosminCOMMUNITY
Explore all skills by this author →
GitHub

retro

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

Updated Mar 24, 2026
Search Tags:#git#performance#metrics#retrospective#engineering#team
One-click install
npx skills add https://github.com/pistosmin/base-one --skill retro-pistosmin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/pistosmin/base-one --skill retro-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams analyze code activity, celebrate wins, and identify growth areas with persistent history across sprints.

Core Features & Use Cases

  • Team-aware: breaks down per-person contributions with praise and growth areas.
  • Proactive insights: suggests focus areas and process improvements at sprint end.
  • History-rich analysis: persistent data across weeks to track trends and outcomes.

Quick Start

Invoke /retro with your preferred window to generate a weekly 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 git commit history, work patterns, and code quality metrics. The Skill breaks down contributions by person and surfaces actionable insights for process improvements at sprint end.

What metrics are included in a team engineering retrospective?▼

A team engineering retrospective includes trends, focus areas, test discipline, session patterns, and per-person praise with growth opportunities. It produces a structured narrative and metrics table with recommended next steps.

Can I run a retrospective for engineering teams using weekly sprints?▼

Yes, the retrospective is designed for engineering teams running weekly sprints. It maintains persistent history across weeks to track trends and outcomes, ensuring complete handling of edge cases and robust error paths.

How do I analyze per-person code contributions for a sprint review?▼

Analyze per-person code contributions by applying the retrospective to your engineering team. It breaks down individual contributions, highlights praise and growth areas, and suggests focus areas and process improvements.

Does the retrospective Skill require any dependencies or external components?▼

No, the retrospective Skill has no dependencies or external components. It operates independently to analyze commit history and work patterns, generating a structured narrative and metrics table for your engineering team.

How do I handle edge cases when analyzing work patterns for a retrospective?▼

The Skill ensures complete handling of edge cases and robust error paths when analyzing work patterns and code quality metrics. It processes commit history reliably to produce accurate weekly retrospective insights.

Related Skills

Explore More Software Engineering Skills→
cegit27cegit27
3

retro

Analyze git commit history to generate weekly retrospective reports.

Official
Advanced
aiunlocked1412aiunlocked1412
14

agile-coach

Generate sprint planning packages with capacity calculations and ceremony scripts.

Community
Intermediate
JacksonZx535JacksonZx535

retro

Generate engineering retrospective reports from Git commit history and code metrics.

Community
Advanced
SeongHuniSeongHuni

retrospective

Generate sprint or milestone retrospectives by analyzing project data.

Community
Intermediate