skills.rest
cegit27
cegit27OFFICIAL
Explore all skills by this author →
GitHub

retro

Analyze git commit history to generate weekly retrospective reports.

3|14|Updated Mar 10, 2026
Search Tags:#code quality#git#retrospective#engineering#velocity#sprint#team analytics
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill retro-cegit27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill retro-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams lack visibility into actual velocity, code quality trends, and individual contribution patterns across sprints. This Skill automates the weekly retrospective by analyzing git history, commit patterns, and code metrics to surface actionable insights without manual spreadsheet work.

Core Features & Use Cases

  • Commit History Analysis: Automatically reviews commits from the past week to identify shipped features, bug fixes, and refactors.
  • Team Contribution Breakdown: Highlights per-person contributions with specific praise for wins and gentle flags for growth areas.
  • Trend Tracking: Compares current metrics against historical data to show velocity changes and code quality trajectories.
  • Use Case: A team lead running their Friday retro can instantly see that the team shipped 12 features this week, but also spent 30% of time on unplanned bug fixes, prompting a discussion on technical debt allocation.

Quick Start

Use the retro skill to analyze this week's commit history and generate an engineering retrospective report.

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?▼

Tracking team velocity trends across sprints requires analyzing git history and comparing current metrics against historical data. This Skill automatically tracks these metrics over time to show code quality trajectories and velocity changes during sprint reviews.

How do I track team velocity trends across sprints using git history?▼

Tracking team velocity trends across sprints requires analyzing git history and comparing current metrics against historical data. This Skill automatically tracks these metrics over time to show code quality trajectories and velocity changes during sprint reviews.

Can I analyze individual developer contributions from git commits for sprint reviews?▼

To run a weekly code quality and velocity assessment, you need git repository access and persistent session storage to track metrics across retrospective cycles. This Skill uses these prerequisites to analyze work patterns and generate trend data.

Do I need persistent session storage to track code quality metrics over time?▼

To run a weekly code quality and velocity assessment, you need git repository access and persistent session storage to track metrics across retrospective cycles. This Skill uses these prerequisites to analyze work patterns and generate trend data.

What is the best way to automate sprint review reports from git repository data?▼

Automating sprint review reports from git repository data involves reviewing commits to identify shipped features, bug fixes, and refactors. This Skill compares current metrics against historical data to surface actionable insights for engineering teams.

Related Skills

Explore More Software Engineering Skills→
lemiglemig

retro

Analyze commit history and code quality metrics to generate weekly retrospective insights.

Community
Advanced
BradliebsBradliebs

retro

Analyze commit history and work patterns to generate weekly engineering retrospectives.

Community
Advanced
chiruu12chiruu12
1

retro

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

Community
Advanced
SoSoBurnerSoSoBurner

gstack-openclaw-retro

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

Community
Advanced