skills.rest
antriksh-29
antriksh-29COMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze git history to generate team retrospectives with per-person metrics and trends.

Updated Mar 24, 2026
Search Tags:#git#metrics#commits#engineering#code-quality#team#retro
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill retro-antriksh-29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill retro-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of engineering retrospectives by analyzing commit history, work patterns, and quality metrics, with persistent history and per-person praise and growth opportunities.

Core Features & Use Cases

  • Analyze git history and contribution data to produce team-wide insights and per-person metrics.
  • Generate a structured weekly or sprint-end retrospective with trend analysis and growth recommendations.
  • Proactively suggest insights at the end of a work week or sprint to guide improvements.

Quick Start

Ask Claude to run /retro to generate the latest weekly retrospective for the current sprint.

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 git commit history?▼

To generate a weekly engineering retrospective, the Skill analyzes git commit history and contribution data to produce team-wide insights, per-person praise, growth opportunities, and trend analysis. Simply run the /retro command to summarize the current sprint.

Can I analyze code quality and test activity metrics for individual developers across multiple repositories?▼

Yes, you can analyze per-author metrics such as commits, LOC, and test activity across one or more repositories. The Skill captures individual contribution data to provide actionable insights and personalized growth recommendations for each team member.

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

A team-aware sprint retrospective uses engineering metrics like commit history and code quality data to evaluate team performance. It automatically generates per-person praise and growth opportunities while maintaining trend history across multiple projects and custom time windows.

Does this approach support custom time windows for retrospective analysis beyond weekly sprints?▼

Yes, retrospective analysis supports both weekly sprints and custom time windows. You can analyze engineering activity and generate team-wide insights with trend history across multiple projects for any specified period.

What's the best way to automate actionable insights for a development team's end-of-week review?▼

The best way to automate actionable insights is to use a Skill that proactively suggests engineering summaries at the end of a work week or sprint. It analyzes work patterns and quality metrics to guide continuous improvements with structured trend analysis.

Why does tracking per-person LOC and commit metrics matter for engineering retrospectives?▼

Tracking per-person LOC and commit metrics matters because it enables data-driven retrospectives by highlighting individual contributions and test activity. This allows the Skill to generate personalized growth opportunities and team-wide praise based on actual engineering activity.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
mgher668mgher668

retro

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

Community
Advanced
michsindlingermichsindlinger
1

Quality Metrics Skill

Automate code quality tracking and reporting across CI/CD pipelines.

Community
Advanced
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced