retro

Analyze commit history and code quality metrics for weekly engineering retrospectives.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Glob, AskUserQuestion, and includes scripts (resource) components.

What problem does it solve?

This Skill helps manage weekly engineering retrospectives by analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking.

Core Features & Use Cases

  • Commit History Analysis: Provides insights into commit history and work patterns.
  • Trend Tracking: Monitors and reports on trends over time.
  • Personal Contributions Analysis: Breaks down per-person contributions for praise and growth areas.
  • Proactive Suggestions: Offers suggestions for proactive planning at the end of a work week or sprint.

Quick Start

Run the /retro skill to initiate an engineering retrospective.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I analyze commit history for a weekly engineering retrospective?

To analyze commit history for a weekly engineering retrospective, this Skill processes your repository logs to evaluate work patterns and code quality metrics. It structures the reflection by breaking down per-person contributions and identifying actionable growth areas.

What is the best way to track engineering productivity trends over time?

Tracking engineering productivity trends requires persistent history analysis of code quality metrics and work patterns. This Skill monitors commit data across sprints, storing retrospective history to report on long-term productivity shifts and proactive planning suggestions.

Can I use Bash and Glob to automate retrospective reporting for my software engineering team?

Yes, you can use Bash and Glob to automate retrospective reporting for your software engineering team. The Skill leverages these tools alongside Read and Write to extract commit data, analyze contributions, and persist retrospective trend history automatically.

How do I generate proactive planning suggestions from sprint commit data?

Generating proactive planning suggestions from sprint commit data involves analyzing work patterns and per-person contributions at the end of a work week. The Skill evaluates code quality metrics from your commits to offer targeted areas for praise and improvement.

Does this retrospective approach work for individual developer contribution analysis?

Yes, this retrospective approach works for individual developer contribution analysis by breaking down per-person commit data. It evaluates individual work patterns against code quality metrics to highlight specific praise areas and targeted growth opportunities.