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

gstack-openclaw-retro

Automates weekly engineering retrospective metrics from git commit history with configurable windows and saved snapshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams waste hours manually compiling weekly retrospective data, pulling commit statistics, tracking individual contributions, and identifying code quality trends from scattered git logs. This skill automates the entire process directly from your repository's git history, eliminating manual data entry and ensuring consistent, data-backed retro discussions.

Core Features & Use Cases

  • Automated Metric Calculation: Pulls commit counts, lines of code changed, PR merge data, test ratios, session patterns, and contributor breakdowns with zero manual configuration.
  • Team-Aware Contribution Analysis: Identifies each team member's work focus areas, highlights top contributions with specific praise anchored in actual commits, and flags actionable growth opportunities.
  • Longitudinal Trend Tracking: Saves retro snapshots to a local memory directory to compare week-over-week progress on shipping velocity, code quality, and team habits. Use case: An engineering lead can run this skill every Monday to generate a full retro of the prior week's work, including who shipped what, code quality signals, and 3 actionable improvements for the team, in seconds instead of hours.

Quick Start

Use the gstack-openclaw-retro skill to generate a weekly engineering retrospective for your current git repository covering the last 7 days.

Frequently Asked Questions about gstack-openclaw-retro

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

FAQPage Schema
How do I automate weekly engineering retrospective metrics from git history?▼

Automating engineering retrospective metrics from git history involves calculating commit statistics, LOC changes, and contributor breakdowns directly from your repository. This eliminates manual data aggregation by pulling commit counts, test ratios, and session patterns for sprint reviews.

Can I track individual contributor performance and code quality trends using git commit analysis?▼

Tracking individual contributor performance and code quality trends via git commit analysis identifies each team member's work focus areas. It highlights top contributions anchored in actual commits and flags actionable growth opportunities for performance tracking.

What is the best way to generate data-backed sprint review metrics without manual data entry?▼

Generating data-backed sprint review metrics without manual data entry requires pulling commit statistics, lines of code changed, and PR merge data directly from git logs. This ensures consistent, automated metric calculation for team progress reviews in seconds.

Does this git analysis tool support configurable time windows for historical comparison?▼

This git analysis tool supports configurable time windows ranging from 24 hours to 30 days, plus historical comparison modes. It persists retrospective snapshots to a local memory directory, enabling longitudinal analysis of week-over-week progress and shipping velocity.

How do I compare week-over-week engineering productivity and code quality deltas?▼

Comparing week-over-week engineering productivity and code quality deltas requires saving retro snapshots to a local memory directory. This calculates trend deltas across historical periods, enabling data-backed retro discussions on shipping velocity and team habits.

Related Skills

Explore More Software Engineering Skills→
RockaRhymeLLCRockaRhymeLLC

weekly-retro

Generate weekly retrospective reports from todos, git commits, and timeline entries.

Official
Intermediate
89jobrien89jobrien
4

agile-ceremonies

Structure Agile standups, retrospectives, and sprint tracking with action items.

Community
Intermediate
blakeoxblakeox

retro

Analyze git history to generate engineering team retrospective reports.

Community
Intermediate
ShmurdocShmurdoc

gstack-openclaw-retro

Automate weekly engineering retros from git commit history.

Community
Advanced