gstack-openclaw-retro

Generate weekly engineering retrospectives from commit history and code quality metrics.

Updated Apr 2, 2026

Search Tags:#git #metrics #retrospective #engineering #code-quality #team

Ready to run

npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill gstack-openclaw-retro-jonkiky

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill gstack-openclaw-retro-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives for the engineering team, analyzing commit history, work patterns, and code quality metrics to surface praise, growth opportunities, and actionable improvements.

Core Features & Use Cases

Team-aware analysis of per-person contributions and growth areas
History-preserving trend tracking across windows (7d/24h/14d/30d)
Per-author and top-file hotspot analysis to guide improvements

Quick Start

Summarize the past week of commits, code quality metrics, and team contributions to generate a weekly engineering 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 generate a weekly engineering retrospective from git commit history?▼

Automate a weekly engineering retrospective by analyzing git commit history, contributor activity, and code quality metrics over a time window like the last 7 days to surface actionable insights and team growth areas.

What is a team-aware code retrospective and how does it analyze contributor activity?▼

A team-aware code retrospective analyzes per-person contributions and growth areas from git history, preserving trend tracking across time windows to guide improvements and highlight praise opportunities for engineering teams.

Can I analyze code quality metrics and commit history for a custom time window like 24h or 30d?▼

Yes, you can analyze code quality metrics and commit history for custom time windows including 24h, 7d (default), 14d, or 30d, with a compare option to track engineering trends across different historical periods.

How do I find top-file hotspots and per-author contributions to guide code improvements?▼

Identify top-file hotspots and per-author contributions by analyzing commit history and code quality metrics, which highlights active files and individual work patterns to guide targeted engineering improvements.

Do I need any specific dependencies or components to run an automated sprint retrospective?▼

No specific dependencies or components are required to run an automated sprint retrospective, as the skill independently gathers git data, computes engineering metrics, and compiles narrative-focused output.