gstack-openclaw-retro

Analyze weekly engineering activity to generate retrospective reports with trend tracking.

Updated Apr 12, 2026

Search Tags:#automation #git #metrics #retrospective #engineering #history #team-awareness

Ready to run

npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill gstack-openclaw-retro-adryanmoldokkr32-pixel

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are automatically generated, analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking, enabling team-aware reflection with per-person praise and growth opportunities.

Core Features & Use Cases

Analyzes commit history, work patterns, and code quality metrics to surface actionable insights.
Identifies the running user, analyzes every contributor, and provides per-person praise and growth opportunities.
Maintains persistent retro history and supports trend analysis across weeks for continuous improvement.
Use when asked for a weekly retro, to understand what shipped and where improvements are needed.

Quick Start

Run the weekly retro command to generate the team retrospective.

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 history?▼

Generate a weekly engineering retrospective by running the retro command, which analyzes commit history, work patterns, and code quality metrics to surface actionable insights, per-person praise, and growth opportunities for software teams.

What engineering metrics are used to track team codebase activity?▼

Engineering metrics tracked include commits, lines of code (LOC), session length, and focus scores, which are computed to evaluate weekly contributor activity and generate team-aware insights.

Can I track long-term engineering trends across multiple weeks?▼

Yes, you can track long-term trends because historical retrospectives are saved in memory, enabling comparison with prior weeks for continuous improvement and long-term trend tracking across multiple weeks.

Does the weekly retrospective provide insights for individual contributors?▼

Yes, the weekly retrospective provides per-author insights by identifying the running user, analyzing every contributor, and offering individualized praise and targeted growth opportunities based on their commit activity.

What do I need to generate a team-aware retrospective report?▼

You need a software team's git commit history and engineering activity for the week; the Skill enforces discovery via SKILL.md frontmatter to compute codebase metrics and generate the retrospective report.