retro

Analyze commit history and code quality trends to generate weekly retrospective summaries.

Updated Mar 27, 2026

Search Tags:#retrospective #engineering #growth #code-quality #commit-history #team-feedback

Ready to run

npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill retro-alejandrofigini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/retro
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill retro-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes commit history, team activity, and code quality trends to produce a structured weekly retrospective that highlights contributions, achievements, and areas for growth.

Core Features & Use Cases

Persistent history and trend tracking across sprints.
Per-person contribution breakdown with praise and growth areas.
Actionable summaries suitable for team retrospectives and process improvements.

Quick Start

Summarize the most recent sprint by analyzing commit history, work patterns, and code quality trends to produce a concise 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 commit history?▼

Generate a weekly engineering retrospective by analyzing commit history and team activity to produce a structured summary of contributions and code quality trends. This process highlights per-person achievements, growth areas, and actionable process improvements suitable for sprint reviews.

What is a sprint-based engineering retrospective and how does it track growth?▼

A sprint-based engineering retrospective analyzes commit data and timeline events to track persistent history and growth trends across iterations. It identifies per-person contributions, code quality signals, and process learnings to provide structured team feedback.

Can I track code quality signals and per-person contribution trends for my team?▼

Yes, you can track code quality signals and per-person contribution trends by analyzing commit history and timeline events. This produces per-person contribution breakdowns with praise areas, growth opportunities, and historical trend tracking across sprints.

What is the best way to summarize engineering activity for process improvements?▼

The best way to summarize engineering activity for process improvements is to analyze commit history and work patterns to produce actionable retrospective summaries. This approach integrates code quality trends and team feedback to highlight specific areas for growth.

Does this retrospective approach work for sprint-based teams needing historical trend tracking?▼

Yes, this retrospective approach is designed for sprint-based teams needing historical trend tracking. It supports persistent history by integrating commit data, timeline events, and learnings to produce per-person contribution insights and process improvements.