skills.rest
shekerkamma
shekerkammaCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze git commit history and code quality metrics to generate weekly engineering retrospective reports.

Updated May 22, 2026
Search Tags:#code quality#retrospective#engineering#commit analysis#sprint review#team metrics
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill retro-shekerkamma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/retro
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill retro-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling weekly engineering retrospectives is time-consuming and inconsistent, especially when tracking commit history, work patterns, code quality, and individual team contributions across sprints. This skill automates that entire process, eliminating manual data gathering and ensuring consistent, actionable retro reports every week.

Core Features & Use Cases

  • Automated Commit & Code Quality Analysis: Pulls and analyzes git commit history, work patterns, and code quality metrics to identify what shipped, bottlenecks, and areas for improvement.
  • Team-Aware Contribution Tracking: Breaks down work per team member, highlighting praise-worthy contributions and growth areas for each individual.
  • Persistent Trend Tracking: Maintains historical retro data to spot trends across sprints, helping teams measure progress over time.
  • Use Case: Engineering teams running weekly sprint retros can use this skill to generate a full retrospective report in minutes instead of hours, with no manual data entry required.

Quick Start

Ask the retro skill to generate a weekly engineering retrospective for your current sprint, including per-team-member contribution breakdowns and trend analysis against past retros.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate sprint retrospective reporting using git commit history?▼

Automating sprint retrospective reporting with git commit history involves analyzing work patterns and code quality metrics to track shipped work. This eliminates manual data gathering by automatically generating consistent, team-aware retro reports with per-person contribution breakdowns.

What is automated engineering retrospective generation and how does it work?▼

Automated engineering retrospective generation pulls git commit history and code quality metrics to identify shipped work and bottlenecks. It breaks down contributions per team member to highlight praise-worthy work and growth areas without manual data entry.

Can I track per-person engineering contributions and performance trends across multiple sprints?▼

Yes, you can track per-person engineering contributions and performance trends across multiple sprints by maintaining historical retro data. This persistent trend tracking helps measure team progress over time while identifying individual growth areas for each contributor.

How do I generate a weekly engineering retro with actionable insights for each contributor?▼

To generate a weekly engineering retro with actionable insights, request a sprint review report that analyzes commit history and work patterns. The output provides per-team-member contribution breakdowns with specific praise and growth area identification for each contributor.

Does automated retrospective generation work for engineering teams without manual code quality data entry?▼

Yes, automated retrospective generation works for engineering teams without manual code quality data entry. It pulls git commit history and analyzes work patterns automatically, generating full retrospective reports in minutes instead of hours with no manual data gathering required.

Related Skills

Explore More Software Engineering Skills→
ligianehualigianehua

retro

Analyze git commit history to generate a team-aware weekly retrospective.

Community
Advanced
KrismithReddy12KrismithReddy12

retro

Analyze engineering commit history and project timeline data to generate automated retrospective reports.

Community
Advanced
greencmgreencm
1

gstack-openclaw-retro

Automates engineering retrospectives by analyzing commit history, work patterns, and code quality metrics.

Community
Advanced
256javy256javy

retro

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

Community
Advanced