gstack-openclaw-retro

Generate weekly engineering retrospectives from git commit history and test signals.

Updated May 19, 2026
One-click install
npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-openclaw-retro-anilveersingh1308
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-openclaw-retro-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retros often become generic, biased, or time-consuming because they lack a consistent, data-driven view of commits, testing, PRs, and contributor patterns.

Core Features & Use Cases

  • Weekly retrospective generation from git history: Produces a comprehensive retro by analyzing commit activity, code changes, and test signals for a specified time window (default last 7 days).
  • Team-aware per-person insights: Identifies the current user, then builds a per-author leaderboard with praise and growth opportunities based on their actual changes.
  • Operational metrics and narrative output: Computes metrics like insertions/deletions, test LOC ratio, hourly distribution, session detection, hotspot analysis, focus score, and streak tracking, then formats results for Telegram.

Quick Start

Ask GitHub Copilot to run the weekly engineering retrospective for the last 14 days and include compare mode output against the prior 14-day window.

Frequently Asked Questions about gstack-openclaw-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 history?

Generate a weekly engineering retrospective by analyzing git commit history, commit types, and test code signals across selectable time windows like 7 or 14 days. The tool computes metrics in your local timezone and outputs a structured narrative summary.

What engineering metrics are included in a git commit analysis retrospective?

A git commit analysis retrospective includes insertions, deletions, test LOC ratio, hourly distribution, hotspot analysis, focus score, streak tracking, and PR size estimates. It detects coding sessions using a 45-minute gap threshold to map contributor activity.

Can I compare engineering metrics across different time windows for trend analysis?

Yes, compare mode allows you to compare engineering metrics across different time windows such as 24h, 7d, 14d, or 30d. Retro history snapshots are saved to memory, enabling trend deltas between the current and prior periods.

How does team-aware contributor analysis work for weekly code reviews?

Team-aware contributor analysis identifies each author and builds a per-person leaderboard based on their actual git changes. It provides individualized praise and growth opportunities by evaluating commit patterns, test signals, and session data.

Do I need a specific git repository setup to track coding sessions and hotspots?

You need a standard git repository with sufficient commit history for the selected time window. The tool analyzes commit timestamps to detect coding sessions with a 45-minute gap threshold and identifies hotspots without requiring external tracking plugins.

What's the best way to run an automated engineering retro for a 14-day sprint window?

Run an automated engineering retro by requesting a 14-day window with compare mode enabled. The tool analyzes the current 14-day git history against the prior 14-day window, computing focus scores, test coverage signals, and session metrics for a structured narrative output.