retro

Name: retro
Availability: InStock
Author: sosoburner

Generate weekly engineering retrospective reports from commit history and code quality metrics.

Updated Apr 8, 2026

Search Tags:#code analysis #retrospective #commit history #project review #team feedback

Ready to run

npx skills add https://github.com/SoSoBurner/GStack --skill retro-sosoburner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/SoSoBurner/GStack/tree/main/retro
Command: npx skills add https://github.com/SoSoBurner/GStack --skill retro-sosoburner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps analyze and summarize the past week's engineering work, identifying key learnings, team contributions, and areas for improvement.

Core Features & Use Cases

Weekly Retrospective: Analyzes commit history, work patterns, and code quality metrics for a specified time period.
Team-Aware Analysis: Identifies individual contributions and provides praise and growth opportunities.
Automated Reporting: Generates a structured report that can be used for discussions and planning.

Quick Start

Run /retro to initiate 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 commit history?▼

A weekly engineering retrospective analyzes commit history, work patterns, and code quality metrics to identify key learnings, team contributions, and areas for improvement. It provides project teams with a structured report to review progress and plan next steps.

How does automated code analysis identify team contributions and growth areas?▼

Automated code analysis evaluates commit history and work patterns to highlight individual team contributions. It identifies specific praise and growth opportunities, helping project teams recognize efforts and pinpoint areas for improvement during the retrospective.

Can I use this project review Skill for tracking code quality metrics?▼

Yes, this project review Skill evaluates code quality metrics alongside commit history and team contributions. It generates a comprehensive report that identifies areas for improvement, making it suitable for tracking weekly engineering progress and code health.

What's the best way to run an automated project retrospective for my engineering team?▼

The best way to run an automated project retrospective is to execute the `/retro` command. It automatically analyzes your team's commit history and code quality metrics, then generates a structured report suitable for team discussions and planning.

Does generating a team feedback retrospective require any external dependencies?▼

Generating a team feedback retrospective requires no external dependencies or components. The Skill operates independently to analyze commit history and code quality metrics, producing a structured weekly report without needing additional tools.