retro

Name: retro
Availability: InStock
Author: benrapport

Analyze commit history and code quality metrics to generate retrospective reports.

Updated Mar 31, 2026

Search Tags:#git #analysis #metrics #engineering #code-quality #team #retro

Ready to run

npx skills add https://github.com/benrapport/Vote-Better --skill retro-benrapport

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/benrapport/Vote-Better --skill retro-benrapport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros analyze commit history, team work patterns, and code quality metrics to surface actionable insights and celebrate progress.

Core Features & Use Cases

Team-aware per-person contributions with praise and growth areas.
Persistent history and trend tracking across sprints.
Proactive end-of-week suggestions to guide upcoming work.

Quick Start

Run the /retro command to generate a weekly engineering retrospective for your repository.

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?▼

You can analyze team work patterns by running the /retro command, which parses commit history and code quality metrics to surface actionable insights. It identifies per-person contributions and highlights both progress to celebrate and areas for growth.

Can I track engineering performance trends across multiple sprint cycles?▼

Yes, you can track engineering performance trends across multiple sprint cycles. The retrospective process maintains persistent history, allowing you to compare code quality metrics and work patterns over time to identify long-term team performance trends.

Does generating a code quality retrospective require remote repository access?▼

Generating a code quality retrospective does not strictly require remote repository access. The analysis can be performed using either a local or remote git history, provided the tool has access to the repository data needed to evaluate commit history and work patterns.

What is the best way to analyze per-person contributions in a software engineering team?▼

The best way to analyze per-person contributions in a software engineering team is by evaluating commit history and code quality metrics. This approach surfaces actionable insights by identifying individual praise areas and growth suggestions based on actual repository data.

How do I propose actionable items at the end of a sprint?▼

To propose actionable items at the end of a sprint, analyze your team's commit history and code quality metrics. This process generates proactive end-of-week suggestions and a structured report to guide upcoming work based on identified performance trends.