retro

Analyze commit history, work patterns, and code quality metrics for weekly retrospectives.

Updated Apr 8, 2026

Search Tags:#code quality #engineering #commit history #retro #team insights

Ready to run

npx skills add https://github.com/sadie100/claude-dotfiles --skill retro-sadie100

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gstack, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the weekly engineering retrospective process, providing insights into project history, team contributions, and learning trends.

Core Features & Use Cases

Commit History Analysis: Reviews commit history to understand project progress.
Work Pattern Tracking: Identifies work patterns and contributions by team members.
Code Quality Metrics: Analyzes code quality metrics for continuous improvement.
Use Case: Use this Skill to summarize the past week's work, highlight achievements, and discuss areas for improvement.

Quick Start

Run the 'weekly retro' command to initiate the engineering retrospective.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate engineering retrospective analysis using commit history?▼

Automating an engineering retrospective analyzes project commit history, work patterns, and code quality metrics to provide team insights. It summarizes weekly progress, highlights achievements, and identifies areas for continuous improvement.

What is a weekly engineering retrospective and how does it track team contributions?▼

A weekly engineering retrospective tracks team contributions by analyzing commit history and work patterns. It identifies individual contributions and learning trends, providing data-driven insights into project progress and team performance.

How do I generate code quality metrics for a project retrospective?▼

Generating code quality metrics for a retrospective requires analyzing project repositories and code quality tools. This process evaluates code standards and work patterns to highlight achievements and discuss areas needing improvement.

Do I need git and gstack to run a weekly engineering retrospective?▼

Yes, you need git and gstack dependencies to run a weekly engineering retrospective. Access to project repositories and code quality tools is required to analyze commit history and generate accurate team insights.

What's the best way to summarize the past week's engineering work?▼

The best way to summarize the past week's engineering work is analyzing commit history and code quality metrics. This approach identifies work patterns, tracks team contributions, and provides insights into learning trends.

Can I use this for tracking learning trends in software engineering teams?▼

Yes, you can use this for tracking learning trends in software engineering teams. By analyzing commit history and work patterns, it provides insights into team contributions and continuous improvement trends over time.