skills.rest
256javy
256javyCOMMUNITY
Explore all skills by this author →
𝕏@NelsonChess666GitHub

gstack-openclaw-retro

Extract commit history and author data into a structured weekly retro.

Updated Apr 15, 2026
Search Tags:#git#metrics#engineering#trends#team#retro
One-click install
npx skills add https://github.com/256javy/safia --skill gstack-openclaw-retro-256javy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/256javy/safia/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/256javy/safia --skill gstack-openclaw-retro-256javy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives are hard to generate from raw git history. This Skill automates gathering commit activity, recognizes per-person contributions with praise, and surfaces growth opportunities in a reusable retrospective.

Core Features & Use Cases

  • End-to-end retro generation from commit history and code activity with per-person insights.
  • Time-windowed analysis (default 7 days, 24h, 14d, 30d) with optional comparison to the prior window.
  • Leaderboard, focus scores, hotspot analysis, and narrative-driven insights that guide improvements.

Quick Start

Run the retro tool for the current repository to generate this week's engineering retrospective and save the results to memory/retro-YYYY-MM-DD.json

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

To generate a weekly engineering retrospective from git commit history, use a tool that extracts commit data and author stats within a 7-day window, producing a structured report with per-author engagement metrics and narrative insights.

Can I compare git metrics and team trends across different time windows?▼

Yes, you can compare git metrics across selectable time windows like 24h, 14d, or 30d. The analysis compares the current window against the prior one to show deltas in team focus scores and activity.

What is commit hotspot analysis and how does it improve a team retro?▼

Commit hotspot analysis identifies areas of high code activity within the repository. It improves a team retro by surfacing specific growth opportunities and focus metrics, guiding actionable engineering improvements.

Does the generated engineering retro support exporting to a Telegram-friendly format?▼

Yes, the generated retro supports a Telegram-friendly narrative format. It processes git logs to compute engagement metrics and outputs a narrative summary suitable for sharing in Telegram.

How are per-author contributions recognized when parsing git logs for a retro?▼

When parsing git logs for a retro, per-author contributions are recognized through computed engagement metrics and a leaderboard. The tool generates narrative insights that include individualized praise for team members.

Related Skills

Explore More Software Engineering Skills→
yocxy2yocxy2

gstack-openclaw-retro

Analyze git commit history to generate engineering retrospectives.

Community
Advanced
chriswesttchriswestt

gstack-openclaw-retro

Aggregate commit history and code quality signals into team retrospectives.

Community
Advanced
haJ1thaJ1t

auto-changelog

Generate CHANGELOG.md from git commit history using Conventional Commits.

Community
Advanced
SoSoBurnerSoSoBurner

gstack-openclaw-retro

Analyze git commit history and code quality metrics for engineering retrospectives.

Community
Advanced