gstack-openclaw-retro

Analyzes commit history to generate weekly engineering retrospectives with per-person metrics and Telegram-ready narratives.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/binfen1/my-skills --skill gstack-openclaw-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/binfen1/my-skills --skill gstack-openclaw-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives require collating commit data, metrics, and team signals to identify praise, growth opportunities, and process improvements. This skill analyzes commit history with per-person contributions and persistent history for trend tracking, enabling team-aware insights.

Core Features & Use Cases

  • Per-person metrics: contributions, praise, and growth opportunities for each team member.
  • History and trends: maintain persistent history to compare weeks side-by-side.
  • Team-aware reporting: generates narratives suitable for team reviews and summaries.

Quick Start

Run the retro for the current 7-day window to generate a narrative and metrics report.

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

Automate weekly engineering retrospectives by analyzing git commit history to generate a team-aware report. The retro covers weekly sprints, capturing per-person contributions, praise, and growth opportunities using deterministic time windows.

What is the best way to track team growth opportunities from commit analysis?

Tracking team growth opportunities from commit analysis involves evaluating per-author metrics and persistent history. This approach identifies per-person contributions and maintains trend data to compare weeks side-by-side for actionable insights.

Can I generate Telegram-friendly engineering summaries from git analysis?

You can generate Telegram-friendly engineering summaries from git analysis. The process produces a narrative suitable for executive summaries, covering weekly sprints and shipped work based on deterministic time windows.

How do per-author metrics work in a team retrospective?

Per-author metrics in a team retrospective work by evaluating individual commit contributions within deterministic time windows. This captures per-person contributions, praise, and growth opportunities to provide team-aware insights.

Does weekly sprint retrospective reporting require persistent history tracking?

Weekly sprint retrospective reporting uses persistent history tracking to enable side-by-side week comparisons. Maintaining historical metrics data allows you to monitor team growth trends and identify process improvements over time.

When do I need deterministic time windows for git analysis?

Deterministic time windows for git analysis are needed when generating consistent weekly retrospectives. They ensure accurate per-person metrics by bounding commit history evaluation to specific seven-day sprint periods.