skills.rest
abhishekmmgn
abhishekmmgnCOMMUNITY
Explore all skills by this author →
𝕏@abhishekmmgnGitHub

gstack-openclaw-retro

Analyze git history to generate team retrospectives with per-person contributions.

Updated Jun 18, 2026
Search Tags:#git#workflow#metrics#engineering#leadership#team#retro
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill gstack-openclaw-retro-abhishekmmgn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill gstack-openclaw-retro-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective generation and team-aware analysis of commit history, PRs, tests, and code quality signals, with growth opportunities and persistent history.

Core Features & Use Cases

  • Per-person contribution breakdown with praise and growth opportunities.
  • Time-window based retrospectives (7d default, 24h, 14d, 30d, compare options) to track trends.
  • Team narrative generation suitable for documentation and messaging (Telegram-ready).
  • Memory of prior retros to compute deltas and trend insights.

Quick Start

Run the retro for the current window to generate the team narrative and metrics.

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 team engineering retrospective from git history?▼

To generate a team engineering retrospective from git history, this Skill analyzes commits, LOC, test signals, and PRs to produce per-person contributions and growth insights. It computes metrics and creates a narrative tailored to your local timezone.

What is included in a per-person engineering contribution breakdown?▼

A per-person engineering contribution breakdown includes individual commits, lines of code, test signals, PRs, and session counts. It also provides focus scoring, praise, and growth opportunities for each team member.

Can I run engineering retrospectives for different time windows like 24h or 30d?▼

Yes, you can run engineering retrospectives for different time windows. It supports 24h, 7d default, 14d, and 30d windows, plus comparison options to track team trends and compute deltas from prior retros.

How do I create a Telegram-ready narrative for a weekly engineering retro?▼

To create a Telegram-ready narrative for a weekly engineering retro, this Skill compiles team-wide metrics and growth insights into a formatted message. The generated narrative is suitable for documentation and direct messaging.

Does this retrospective tool remember previous engineering metrics to show trends?▼

Yes, this retrospective tool remembers previous engineering metrics. It maintains memory of prior retros to compute deltas and trend insights, allowing you to compare current team performance against historical data.

Related Skills

Explore More Software Engineering Skills→
KrismithReddy12KrismithReddy12

retro

Analyze engineering commit history and project timeline data to generate automated retrospective reports.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
jon23djon23d
3

pipeline-watch

Monitor CI/CD pipeline check statuses for pull requests on GitHub and Gitea.

Community
Intermediate
shihwesleyshihwesley

retro

Analyze Git history to generate weekly engineering retrospectives with per-author metrics.

Community
Advanced