retro

Name: retro
Availability: InStock
Author: bizzybae

Analyze commits, PR activity, and code quality metrics to generate weekly engineering retrospectives.

Updated Apr 5, 2026

Search Tags:#engineering #code-quality #commit-history #retro #praise #team-growth

Ready to run

npx skills add https://github.com/bizzybae/qstack --skill retro-bizzybae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/bizzybae/qstack/tree/main/gstack-original/retro
Command: npx skills add https://github.com/bizzybae/qstack --skill retro-bizzybae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes commit history, work patterns, and code quality metrics to surface team contributions, praise, and growth opportunities for a structured weekly retro.

Core Features & Use Cases

Persistent, team-aware retrospectives that track per-person contributions and code quality over time.
Analyzes commits, PR activity, and workload patterns to surface praise, bottlenecks, and improvement areas.
Generates actionable recommendations for process changes or skill growth aligned with sprint timelines.

Quick Start

Ask for a weekly retro by saying /retro to generate a team 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 and PR activity?▼

Engineering retrospectives analyze commit history and PR activity to surface team contributions, praise, and growth opportunities. This approach tracks per-person contributions and code quality over time to generate structured weekly insights for sprint reviews.

Can I track per-person code quality metrics and contributions over multiple sprints?▼

Yes, you can track per-person code quality metrics and contributions over multiple sprints using persistent, team-aware retrospectives. This maintains a persistent history that enables trend analysis and identifies workload patterns across the team over time.

How do I get actionable recommendations for team growth from code quality metrics?▼

You can get actionable recommendations for team growth by analyzing commit history and code quality metrics to surface improvement areas. The generated retrospective provides targeted suggestions for process changes or skill development aligned with sprint timelines.

Does the weekly retro analysis work for multiple engineering teams and branches?▼

The weekly retro analysis applies across sprints and multiple teams to surface per-person praise and growth opportunities. It delivers per-branch summaries and team metrics while allowing human review and adjustment of the generated retrospective insights.

What is the best way to analyze workload patterns and bottlenecks in engineering commits?▼

The best way to analyze workload patterns and bottlenecks in engineering commits is to generate a structured retrospective that examines historical PR activity and commit history. This process surfaces team contributions, identifies bottlenecks, and highlights improvement areas over a persistent history.