retro

Name: retro
Availability: InStock
Author: him55710-sudo

Analyze commit history and contributor activity to generate engineering retrospectives.

Updated Mar 19, 2026

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

Ready to run

npx skills add https://github.com/him55710-sudo/uni-foli --skill retro-him55710-sudo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/him55710-sudo/uni-foli/tree/main/.agents/skills/gstack-retro
Command: npx skills add https://github.com/him55710-sudo/uni-foli --skill retro-him55710-sudo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated retrospectives that synthesize commit history, work patterns, and code quality into a clear team-facing narrative.

Core Features & Use Cases

Per-contributor praise and growth notes with trend tracking.
Persistent history and trend dashboards across sprints.
Actionable items and team-wide insights for sprint planning.

Quick Start

Invoke the retro skill with the /retro command to generate the 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 an engineering retrospective from git commit history?▼

To generate an engineering retrospective from git commit history, you can use the /retro command. It analyzes contributor activity and code quality signals to produce a team-aware narrative with per-person contributions and actionable improvements.

Can I track individual contributor growth and code quality metrics for weekly sprints?▼

Yes, you can track contributor growth and code quality metrics for weekly sprints. The retrospective process computes these metrics to deliver per-contributor praise notes, growth areas, and trend tracking across your engineering team.

What is a team-aware engineering retrospective and how does it work?▼

A team-aware engineering retrospective synthesizes commit history and work patterns into a team-facing narrative. It evaluates code quality signals to generate per-author leaderboards, highlighting team growth and actionable items for sprint planning.

Does this automated retrospective process support cross-team project reviews?▼

Yes, the automated retrospective process supports cross-team project reviews. It applies to weekly sprints and broader project reviews, computing contributor metrics to present growth areas and actionable insights for multiple engineering teams.

How do I maintain persistent history and trend dashboards across sprints?▼

You can maintain persistent history and trend dashboards across sprints by running the /retro command. It computes and stores engineering metrics over time, allowing you to track team growth and generate actionable items for sprint planning.