gstack-openclaw-retro

Analyze team progress from git commit history for weekly retrospectives.

Updated Apr 24, 2026

Search Tags:#git #metrics #engineering #growth #code-quality #team #retro

Ready to run

npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill gstack-openclaw-retro-sakshamkandel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill gstack-openclaw-retro-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics with persistent history, enabling team-aware praise and growth opportunities.

Core Features & Use Cases

Team-aware with per-person contributions, praise, and growth opportunities.
Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking.
Use the retro for weekly planning, shipping review, or engineering retrospectives to inform improvements.

Quick Start

Generate a weekly retro for the current time window and summarize team contributions.

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

You can automate a weekly engineering retrospective by parsing git logs to track per-person contributions, work patterns, and code quality metrics. This generates team-aware praise and growth opportunities while maintaining persistent history for trend tracking.

What is the best way to track team progress and code quality metrics for a retro?▼

The best way to track team progress for a retro is analyzing commit history to monitor persistent trends and code quality metrics. This approach identifies per-person contributions to inform team-aware praise and targeted growth opportunities.

How do I analyze per-person contributions from git logs for a shipping review?▼

You analyze per-person contributions from git logs by parsing the commit history to track individual work patterns and code quality metrics. This enables team-aware praise and highlights specific growth opportunities for each developer.

Can I generate a what shipped this week summary using git metrics?▼

Yes, you can generate a what shipped this week summary by parsing git metrics and commit history. It analyzes work patterns and code quality to produce a retrospective of team progress with persistent history tracking.

Does an automated engineering retro work with persistent history for trend tracking?▼

An automated engineering retro works with persistent history by continuously parsing git logs to track code quality metrics and work patterns over time. This enables trend tracking to inform improvements during weekly planning.