gstack-openclaw-retro

Name: gstack-openclaw-retro
Availability: InStock
Author: Mostafa

Generate weekly engineering retrospective reports from git commit history.

3|Updated Oct 12, 2025

Search Tags:#code quality #retrospective #engineering #commit analysis #team analytics

Ready to run

npx skills add https://github.com/mostafasudo/warpy --skill gstack-openclaw-retro-mostafasudo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/mostafasudo/warpy/tree/main/.codex/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/mostafasudo/warpy --skill gstack-openclaw-retro-mostafasudo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the analysis of your engineering work, providing a comprehensive weekly engineering retrospective without manual effort.

Core Features & Use Cases

Commit History Analysis: Analyzes commit history, work patterns, and code quality metrics.
Team Awareness: Identifies team members and their contributions, with praise and growth opportunities.
Time Window Flexibility: Supports various time windows (last 7 days, 24 hours, 14 days, 30 days, compare).
Output Formatting: Generates a narrative report formatted for Telegram, including metrics, trends, and team member analyses.

Quick Start

Run the gstack-openclaw-retro skill with the desired time window, e.g., 'gstack-openclaw-retro 14d'.

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 my weekly engineering retrospective using git commit history?▼

Automate your weekly engineering retrospective by analyzing git commit history to identify team members and calculate metrics like commits, LOC, and PRs. The skill generates a structured narrative report without manual data gathering.

Can I generate an engineering retrospective report for a 14-day or 30-day time window?▼

Yes, engineering retrospective reports support flexible time windows including the last 24 hours, 7 days, 14 days, and 30 days. You can specify your desired period when running the skill to analyze the corresponding commit history.

Does this retrospective analysis tool require a specific git environment setup?▼

Commit history analysis requires git installed in your environment to retrieve data and calculate engineering metrics. The skill uses your repository's commit logs to identify team contributions and work patterns automatically.

What metrics are included in an automated team retrospective report?▼

Automated team retrospective reports include metrics such as commit counts, lines of code changed, and pull request activity. The analysis identifies individual team member contributions, highlighting trends, praise, and growth opportunities.

How do I format engineering analytics for Telegram messaging?▼

Format engineering analytics for Telegram messaging by generating a structured narrative report from commit history data. The skill outputs the retrospective analysis directly in a format optimized for Telegram delivery.

Why use automated commit analysis instead of manual weekly engineering reviews?▼

Automated commit analysis eliminates manual effort by directly parsing git history to calculate work patterns and code quality metrics. It provides comprehensive team awareness and growth opportunities without manual data aggregation.