retro

Aggregate commit history and code quality metrics into weekly engineering retrospectives.

Updated Apr 15, 2026

Search Tags:#metrics #engineering #growth #commit-history #retro #team-performance

Ready to run

npx skills add https://github.com/256javy/safia --skill retro-256javy

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are time-consuming to compile and hard to surface actionable insights. This skill analyzes commit history, work patterns, and code quality metrics to provide a persistent retrospective history with trend tracking and per-person growth notes.

Core Features & Use Cases

Persistent history and trend tracking for weekly retros
Team-aware breakdown of contributions with praise and growth areas
Proactive suggestions at the end of a week or sprint
Triggered by prompts like "weekly retro", "what did we ship", or "engineering retrospective"

Quick Start

Summarize this week's work and produce a retro for the current sprint using the repository data.

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, aggregate commit history, work patterns, and code quality metrics to summarize shipped work, growth areas, and per-person contributions. This provides a persistent retro history with trend tracking.

What metrics should an engineering retrospective include for tracking team growth?▼

An engineering retrospective should include commit history, work patterns, and code quality metrics. These metrics surface per-person contributions, highlight growth areas, and enable trend tracking across sprints.

Can I use code quality metrics to summarize per-person contributions for a sprint?▼

Yes, code quality metrics combined with commit history and work patterns are used to produce team-aware summaries. This breaks down individual contributions and identifies specific praise and growth areas for each team member.

What is the best way to track engineering trends across multiple sprints?▼

The best way to track engineering trends is by maintaining a persistent history of weekly retrospectives. Aggregating work patterns and code quality metrics over time generates trend tracking and proactive growth suggestions.

Does an automated engineering retro work for individual developer growth tracking?▼

Automated engineering retros focus on team-aware breakdowns but also provide per-person growth notes. Analyzing individual commit history and code quality metrics highlights specific praise and growth areas for each developer.