skills.rest
Chang-Shih-Yung
Chang-Shih-YungCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Compile weekly engineering retrospectives from git commit history.

Updated Apr 1, 2026
Search Tags:#trend analysis#git analysis#commit tracking#engineering retrospective#team contributions#code quality metrics#shipping velocity
One-click install
npx skills add https://github.com/Chang-Shih-Yung/nexus-finance --skill gstack-openclaw-retro-chang-shih-yung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/Chang-Shih-Yung/nexus-finance/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/Chang-Shih-Yung/nexus-finance --skill gstack-openclaw-retro-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling weekly engineering retrospectives from scattered git history, commit metrics, and team contribution data is time-consuming and error-prone. This Skill automates the entire process to deliver actionable insights in seconds.

Core Features & Use Cases

  • Automated Git Metrics Collection: Pulls commit counts, LOC changes, PR data, test ratios, and session patterns for any customizable time window (24h to 30d).
  • Team Contribution Analysis: Identifies per-person commits, focus areas, praise-worthy wins, and specific growth opportunities for every contributor, with special deep-dive analysis for the user running the command.
  • Trend & Streak Tracking: Saves persistent retro history to track week-over-week improvements in shipping velocity, code quality, and team consistency, including consecutive shipping streak counts.
  • Use Case: For a 5-person engineering team, run this Skill after a sprint to generate a shareable retro that highlights top shipped work, flags code churn hotspots, and identifies if the team is spending too much time on bug fixes vs new feature development.

Quick Start

Use the gstack-openclaw-retro skill to generate a 7-day engineering retrospective for the current git repository.

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

Automating weekly engineering retrospectives from git commit history eliminates manual data aggregation by automatically pulling commit counts, LOC changes, and PR data to generate structured, shareable retro outputs in seconds.

Can I track per-contributor performance and code churn for my engineering team?▼

Per-contributor performance and code churn tracking analyze individual commits, focus areas, and praise-worthy wins, identifying specific growth opportunities and flagging code churn hotspots for every team member.

Does this tool support customizable time windows for measuring shipping velocity?▼

Shipping velocity measurement supports customizable time windows ranging from 24-hour to 30-day intervals, detecting session patterns and tracking consecutive shipping streaks for trend comparison.

What is the best way to compare week-over-week engineering team consistency and code quality metrics?▼

Comparing week-over-week engineering team consistency and code quality metrics requires persistent retro history storage, which saves previous data to track improvements in shipping velocity and team consistency over time.

Can I generate a sprint retrospective that flags bug fixes versus new feature development?▼

Generating a sprint retrospective that flags bug fixes versus new feature development analyzes code churn hotspots and commit patterns to identify if the team is spending too much time on fixes rather than feature development.

Related Skills

Explore More Software Engineering Skills→
shekerkammashekerkamma

gstack-openclaw-retro

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

Community
Advanced
BradliebsBradliebs

retro

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

Community
Advanced
michsindlingermichsindlinger
1

Quality Metrics Skill

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

Community
Advanced
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced