retro

Analyze commit history and code quality metrics to generate weekly retrospectives.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/whd4/gstack --skill retro-whd4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/whd4/gstack/tree/main/retro
Command: npx skills add https://github.com/whd4/gstack --skill retro-whd4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking, helping teams understand delivery health and identify growth opportunities.

Core Features & Use Cases

  • Persistent history and trend tracking of engineering activity across sprints.
  • Team-aware per-person contributions with praise and growth areas.
  • Proactive retro prompts at the end of a sprint or when asked.

Quick Start

Ask for a weekly retro to generate a structured retrospective with growth recommendations.

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?

To generate a weekly engineering retrospective, analyze your team's commit history, work patterns, and code quality metrics to produce a structured review with per-person contributions and growth recommendations.

What is a sprint retrospective analysis based on code quality metrics?

A sprint retrospective analysis based on code quality metrics evaluates engineering activity and delivery health across sprints, providing persistent trend tracking and actionable feedback for team growth.

Can I use this to track per-person engineering contributions during a sprint?

Yes, you can track per-person engineering contributions during a sprint. The analysis identifies individual work patterns and provides specific praise and growth areas for each team member.

When do I need to run a team growth retrospective for software engineering?

You need to run a team growth retrospective at the end of a sprint cadence to review code quality and delivery health, or proactively when prompted to assess engineering trends.

What's the best way to analyze work patterns and code quality for team health?

The best way to analyze work patterns and code quality for team health is to apply persistent history tracking across sprints, identifying delivery trends and generating actionable feedback for improvements.